Skip to main content
CVE-2026-15806VulnerabilityPublished Updated

HTTPPasswordMgr Class

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-15806· Medium 6.0

Not known to be exploited · CVSS 6.0 Medium · fixed in 3.15.0rc2 : update CPython when convenient.

Data as of 10 Nov 2026, 16:36 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (PSF)CVSS 4.06.0
Patch
Available – fixed in 3.15.0rc2, 3.14.8, 3.13.16 +3
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
Python Software FoundationCPythonAffected
  • >=3.15.0a1 <3.15.0rc2
Fixed in
  • 3.15.0rc2
Python Software FoundationCPythonAffected
  • >=3.14.0 <3.14.8
Fixed in
  • 3.14.8
Python Software FoundationCPythonAffected
  • >=3.13.0 <3.13.16
Fixed in
  • 3.13.16
Python Software FoundationCPythonAffected
  • >=3.12.0 <3.12.15
Fixed in
  • 3.12.15
Python Software FoundationCPythonAffected
  • >=3.11.0 <3.11.17
Fixed in
  • 3.11.17
Python Software FoundationCPythonAffected
  • <3.10.22
Fixed in
  • 3.10.22

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The HTTPPasswordMgr class in the urllib.request module, along with its subclasses HTTPPasswordMgrWithDefaultRealm and HTTPPasswordMgrWithPriorAuth, did not take the URL scheme into account when matching stored credentials against a requested URL. Credentials added for an https:// URL were also used for requests to the same host over http://, so an attacker able to redirect or downgrade a client to plain HTTP (for example, via an HTTPS-to-HTTP redirect or an on-path position) could capture credentials in cleartext. Credentials added for http:// URLs could likewise be sent over https://. Credential matching is now scoped by URL scheme. Credentials registered with a URL that includes a scheme are only used for requests with the same scheme. Credentials registered with a bare authority (such as example.com or example.com:8080) continue to match any scheme, preserving compatibility with existing code, including proxy authentication. Users who cannot upgrade immediately can mitigate by ensuring that applications never make plain http:// requests to hosts for which credentials are registered, for example by not following redirects to http:// URLs.

References

Community reviews

Loading reviews…