BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-15806High confidence

`HTTPPasswordMgr` can send saved HTTPS credentials via HTTP because of incorrect scheme matching

Python Software Foundation · CPython

6.0MediumCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 8 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 18 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.46% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Python Software Foundation CPython and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 8 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

16 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 8 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainpython3Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.12.15-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainpython3Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.12.15-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainpython3Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.12.15-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcepypy3Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · sourcepython3.13Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcepypy3Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcepython3.11Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcepypy3Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcepython3.13Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcepython3.14Vendor fix publishedDebian records a fixed source-package version for this release.3.14.7-3Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcepython3.15Vendor fix publishedDebian records a fixed source-package version for this release.3.15.0~rc2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcepypy3Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcepython3.13Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcepython3.14Vendor fix publishedDebian records a fixed source-package version for this release.3.14.7-3Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcepython3.15Vendor fix publishedDebian records a fixed source-package version for this release.3.15.0~rc2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivepython3.12Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-15806 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypython: Python: Information disclosure due to incorrect URL scheme matching
16 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • python3-10-main@aarch64 as a component of Red Hat Hardened Images
  • python3-10-main@src as a component of Red Hat Hardened Images
  • python3-10-main@x86_64 as a component of Red Hat Hardened Images
  • python3-11-main@aarch64 as a component of Red Hat Hardened Images
  • python3-11-main@src as a component of Red Hat Hardened Images
  • python3-11-main@x86_64 as a component of Red Hat Hardened Images
  • python3-12-main@aarch64 as a component of Red Hat Hardened Images
  • python3-12-main@src as a component of Red Hat Hardened Images
  • python3-12-main@x86_64 as a component of Red Hat Hardened Images
  • python3-13-main@aarch64 as a component of Red Hat Hardened Images
  • python3-13-main@src as a component of Red Hat Hardened Images
  • python3-13-main@x86_64 as a component of Red Hat Hardened Images
Summary
A flaw was found in Python. The `HTTPPasswordMgr` class in the `urllib.request` module did not correctly consider the URL scheme when matching stored credentials against a requested URL. This allowed credentials intended for an HTTPS (secure) connection to be sent over an unencrypted HTTP connection to the same host. A remote attacker, by redirecting or downgrading a client to plain HTTP, could exploit this to capture sensitive credentials in cleartext, leading to information disclosure.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-61013

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
6.0 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 8 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

How

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

How

An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
a network path → Cleartext Transmission of Sensitive Information → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Passive interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-319 ↗

CWE-319: Cleartext Transmission of Sensitive Information. The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
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

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedCWE-319Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-61013Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2924CPython: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in CPython ausnutzen, um Informationen offenzulegen und um nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1249Multiples vulnérabilités dans les produits VMware

d?id=CVE-2026-13757 Référence CVE CVE-2026-14164 https://www.cve.org/CVERecord?id=CVE-2026-14164 Référence CVE CVE-2026-14257 https://www.cve.org/CVERecord?id=CVE-2026-14257 Référence CVE CVE-2026-14456 https://www.cve.org/CVERecord?id=CVE-2026-14456 Référence CVE CVE-2026-14457 https://www.cve.org/CVERecord?id=CVE-2026-14457 Référence CVE CVE-2026-15308 https://www.cve.org/CVERecord?id=CVE-2026-15308 Référence CVE CVE-2026-15310 https://www.cve.org/CVERecord?id=CVE-2026-15310 Référence CVE CVE-2026-15534 https://www.cve.org/CVERecord?id=CVE-2026-15534 Référence CVE CVE-2026-15588 https://www.cve.org/CVERecord?id=CVE-2026-15588 Référence CVE CVE-2026-15806 https://www.cve.org/CVERecord?id=CVE-2026-15806 Référence CVE CVE-2026-16118 https://www.cve.org/CVERecord?id=CVE-2026-16118 Référence CVE CVE-2026-1703 https://www.cve.org/CVERecord?id=CVE-2026-1703 Référence CVE CVE-2026-17084 https://www.cve.org/CVERecord?id=CVE-2026-17084 Référence CVE CVE-2026-18477 https://www.cve.org/CVERecord?id=CVE-2026-18477 Référence CVE CVE-2026-18503 https://www.cve.org/CVERecord?id=CVE-2026-18503 Référence CVE CVE-2026-18508 https://www.cve.org/CVERecord?id=CVE-2026-18508 Référence CVE CVE-2026-18798 https://www.cve.org/CVERecord?id=CVE-2026-18798 Référence CVE CVE-2026-18938 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1044Multiples vulnérabilités dans Python

De multiples vulnérabilités ont été découvertes dans Python. Elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, un contournement de la politique de sécurité et un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
CPython: 3.13.0 < 3.13.16, 3.11.0 < 3.11.17, 3.12.0 < 3.12.15, 3.14.0 < 3.14.8, 3.15.0a1 < 3.15.0rc2, 0 < 3.10.22
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 18 Aug 2026 · Last source change 2 Oct 2026, 00:39 UTC · CWE-319 · Cleartext Transmission of Sensitive Information

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-23
European sourceENISA EUVD · EUVD-2026-61013
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2026-15806.
    Before
    remediation: access.redhat.com/CVE-2026-15806
    After
    no authoritative guidance recorded
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.12.15, 3.13.0 < 3.13.16, 3.14.0 < 3.14.8, 3.15.0a1 < 3.15.0rc2 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    After
    CPython: < 3.10.22, 3.11.0 < 3.11.17, 3.12.0 < 3.12.15, 3.13.0 < 3.13.16, 3.14.0 < 3.14.8, 3.15.0a1 < 3.15.0rc2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  3. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.12.15, 3.13.0 < 3.13.16, 3.14.0 < 3.14.8, 3.15.0a1 < 3.15.0rc2 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    After
    CPython: < 3.12.15, 3.13.0 < 3.13.16, 3.14.0 < 3.14.8, 3.15.0a1 < 3.15.0rc2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  5. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2026-15806.
    Before
    remediation: access.redhat.com/CVE-2026-15806
    After
    no authoritative guidance recorded
    CNA ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.15.0rc2 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    After
    CPython: < 3.12.15, 3.13.0 < 3.13.16, 3.14.0 < 3.14.8, 3.15.0a1 < 3.15.0rc2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  7. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  8. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.10.22, 3.11.0 < 3.11.17, 3.12.0 < 3.12.15, 3.13.0 < 3.13.16, 3.14.0 < 3.14.8, 3.15.0a1 < 3.15.0rc2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    CPython: < 3.10.22, 3.11.0 < 3.11.17, 3.12.0 < 3.12.15, 3.13.0 < 3.13.16, 3.14.0 < 3.14.8, 3.15.0a1 < 3.15.0rc2 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  9. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.12.15, 3.13.0 < 3.13.16, 3.14.0 < 3.14.8, 3.15.0a1 < 3.15.0rc2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    CPython: < 3.12.15, 3.13.0 < 3.13.16, 3.14.0 < 3.14.8, 3.15.0a1 < 3.15.0rc2 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  10. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.15.0rc2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    CPython: < 3.15.0rc2 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  11. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-15806 to remediation: access.redhat.com/CVE-2026-15806.
    Before
    remediation: access.redhat.com/CVE-2026-15806
    After
    remediation: access.redhat.com/CVE-2026-15806
    Red Hat Product Security ↗
  12. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  13. Affected versionsThe structured affected or fixed version information changed.
    Before
    python3.10.src as a component of Red Hat Hardened Images; python3.11.src as a component of Red Hat Hardened Images; python3.12.src as a component of Red Hat Hardened Images; python3.13.src as a component of Red Hat Hardened Images; python3.14.src as a component of Red Hat Hardened Images
    After
    Fixed: python3-10-main@aarch64 as a component of Red Hat Hardened Images; python3-10-main@src as a component of Red Hat Hardened Images; python3-10-main@x86_64 as a component of Red Hat Hardened Images; python3-11-main@aarch64 as a component of Red Hat Hardened Images; python3-11-main@src as a component of Red Hat Hardened Images; python3-11-main@x86_64 as a component of Red Hat Hardened Images; python3-12-main@aarch64 as a component of Red Hat Hardened Images; python3-12-main@src as a component of Red Hat Hardened Images; python3-12-main@x86_64 as a component of Red Hat Hardened Images; python3-13-main@aarch64 as a component of Red Hat Hardened Images; python3-13-main@src as a component of Red Hat Hardened Images; python3-13-main@x86_64 as a component of Red Hat Hardened Images; python3-14-main@aarch64 as a component of Red Hat Hardened Images; python3-14-main@noarch as a component of Red Hat Hardened Images; python3-14-main@src as a component of Red Hat Hardened Images; python3-14-main@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
  14. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    CPython: < 3.15.0rc2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  15. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 3.15.0rc2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  16. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.15.0rc2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    CPython: < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  17. Vendor guidanceAuthoritative vendor guidance changed: removed patch: github.com/851cf9a7142ecbdd39f831055533f58284ad2bcc; removed remediation: github.com/851cf9a7142ecbdd39f831055533f58284ad2bcc.
    Before
    patch: github.com/851cf9a7142ecbdd39f831055533f58284ad2bcc · remediation: github.com/851cf9a7142ecbdd39f831055533f58284ad2bcc
    After
    no authoritative guidance recorded
    CNA ↗
  18. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.15.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  19. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  20. Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/851cf9a7142ecbdd39f831055533f58284ad2bcc; added remediation: github.com/851cf9a7142ecbdd39f831055533f58284ad2bcc.
    Before
    no authoritative guidance recorded
    After
    patch: github.com/851cf9a7142ecbdd39f831055533f58284ad2bcc · remediation: github.com/851cf9a7142ecbdd39f831055533f58284ad2bcc
    github.com ↗
  21. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 3.15.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  22. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    github.com ↗
  23. Vendor guidanceAuthoritative vendor guidance changed: removed patch: github.com/641be42bb07921ba0f8bffe228b1dc706b092ef6; removed remediation: github.com/641be42bb07921ba0f8bffe228b1dc706b092ef6.
    Before
    patch: github.com/641be42bb07921ba0f8bffe228b1dc706b092ef6 · remediation: github.com/641be42bb07921ba0f8bffe228b1dc706b092ef6
    After
    no authoritative guidance recorded
    CNA ↗
  24. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.15.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  25. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  26. Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/641be42bb07921ba0f8bffe228b1dc706b092ef6; added remediation: github.com/641be42bb07921ba0f8bffe228b1dc706b092ef6.
    Before
    no authoritative guidance recorded
    After
    patch: github.com/641be42bb07921ba0f8bffe228b1dc706b092ef6 · remediation: github.com/641be42bb07921ba0f8bffe228b1dc706b092ef6
    github.com ↗
  27. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 3.15.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  28. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    github.com ↗
  29. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.16.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  30. Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.
    Before
    No public exploit
    After
    Public exploit reference
    CVE.org ↗
  31. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-61013↗Red Hat Product Security security advisory↗CISA Vulnrichment SSVC evidence↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-15806 · cve.blacktree.nl