Lucene search
K

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).

🗓️ 03 Sep 2025 23:11:12Reported by MicrosoftType 
mscve
 mscve
🔗 msrc.microsoft.com👁 1 Views

urllib3 before 1.24.2 leaves the authorization header on cross-origin redirects, risking credentials.

Related

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

03 Sep 2025 23:11Current
7High risk
Vulners AI Score7
CVSS 25
CVSS 39.8
CVSS 3.16.1
EPSS0.00656
SSVC
1