CVE-2018-25091

What it is

urllib3 before 1.24.2 does not remove the authorization HTTP header when following a cross-origin redirect (i.e., a redirect that differs in host, port, or scheme). This can allow for credentials in the authorization header to be exposed to unintended hosts or transmitted in cleartext. NOTE: this issue exists because of an incomplete fix for CVE-2018-20060 (which was case-sensitive).

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.

Exploit odds

0.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-10-15 19:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:54 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.6% in the next 30 days (EPSS).
• Severity: 6.1 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-10-15 19:15 UTC

Last modified

2026-06-17 01:54 UTC

Exploit probability

0.6% · EPSS, next 30 days

Weakness

CWE-601

Record status

Modified

Affected

• Python urllib3 < 1.24.2

Attack profile CVSS 3.1 · 6.1

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2018-25091.md and follow it. Check whether this project is affected by CVE-2018-25091. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge