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

tarfile hardlink fallback ignores custom extraction filter rejection via None

Python Software Foundation · CPython

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 404 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:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.64% 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.
  • Monitor vendor guidance and exploitation sources for a material change.

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: As exposure requiresRemediation target: Within 365 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 404 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.

17 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 10 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 5 Oct 2026
Debian trixietrixie · sourcepython3.13Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcepypy3Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcepython3.11Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepypy3Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython3.13Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython3.14Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython3.15Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepypy3Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython3.13Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython3.14Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython3.15Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivepypy3Under 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
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.

2 current
CVE-2026-87910 · CSAF 2.0 · revision 5 · interimSUSE Product Security TeamCVE-2026-87910
394 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • python3 as component of SUSE Linux Enterprise Desktop 15 SP7
  • python3-curses as component of SUSE Linux Enterprise Desktop 15 SP7
  • python3-dbm as component of SUSE Linux Enterprise Desktop 15 SP7
  • python3-idle as component of SUSE Linux Enterprise Desktop 15 SP7
  • python3-tk as component of SUSE Linux Enterprise Desktop 15 SP7
  • python311 as component of SUSE Linux Enterprise Desktop 15 SP7
  • python311-curses as component of SUSE Linux Enterprise Desktop 15 SP7
  • python311-dbm as component of SUSE Linux Enterprise Desktop 15 SP7
  • python311-idle as component of SUSE Linux Enterprise Desktop 15 SP7
  • python311-tk as component of SUSE Linux Enterprise Desktop 15 SP7
  • python313 as component of SUSE Linux Enterprise Desktop 15 SP7
  • python313-curses as component of SUSE Linux Enterprise Desktop 15 SP7
Summary
When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was ignored. Instead, the member should be skipped if either call returns None.
Remediation
No remediation text is recorded.
CVE-2026-87910 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypython: Python tarfile module: Security filter bypass allows arbitrary file write
95 fixed

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

  • python-unversioned-command-0:3.14.7-1.2.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images
  • python-unversioned-command-0:3.14.7-1.2.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images
  • python3-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images
  • python3-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images
  • python3-debug-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images
  • python3-debug-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images
  • python3-devel-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images
  • python3-devel-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images
  • python3-idle-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images
  • python3-idle-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images
  • python3-libs-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images
  • python3-libs-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images
Summary
A flaw was found in the Python `tarfile` module. When extracting an archive containing a link on systems that do not support links, the module falls back to extracting the linked member. During this fallback, a security filter designed to prevent the extraction of certain files is not properly applied. This oversight could allow an attacker to bypass intended security restrictions, potentially leading to the creation or modification of arbitrary files on the system.
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-76162

No EUVD known-exploited evidence

When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was ignored. Instead, the member should be skipped if either call returns None.

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
5.7 · 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 no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 404 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

When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was ignored. Instead, the member should be skipped if either call returns None.

What

When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was ignored. Instead, the member should be skipped if either call returns None.

Why

Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was ignored. Instead, the member should be skipped if either call returns None.

Why

Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.

How

An attacker operating through a network path may attempt exploitation with low privileges. 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.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
Active interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-22 ↗

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

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:L/AT:P/PR:L/UI:A/VC:N/VI:H/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.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRLowPrivileges required: The attacker needs basic user-level privileges.UIActiveUser interaction: A user must take a deliberate action for exploitation to succeed.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VIHighVulnerable-system integrity: A successful attack can cause a major loss.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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-22
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-76162Official EUVD mapping

When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was ignored. Instead, the member should be skipped if either call returns None.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3335CPython: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in CPython ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260916Security Bulletin 16 Sep 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 16 Sep 2026, published on 16 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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

ERecord?id=CVE-2026-81870 Référence CVE CVE-2026-82049 https://www.cve.org/CVERecord?id=CVE-2026-82049 Référence CVE CVE-2026-8286 https://www.cve.org/CVERecord?id=CVE-2026-8286 Référence CVE CVE-2026-83557 https://www.cve.org/CVERecord?id=CVE-2026-83557 Référence CVE CVE-2026-84303 https://www.cve.org/CVERecord?id=CVE-2026-84303 Référence CVE CVE-2026-84304 https://www.cve.org/CVERecord?id=CVE-2026-84304 Référence CVE CVE-2026-84445 https://www.cve.org/CVERecord?id=CVE-2026-84445 Référence CVE CVE-2026-8643 https://www.cve.org/CVERecord?id=CVE-2026-8643 Référence CVE CVE-2026-8763 https://www.cve.org/CVERecord?id=CVE-2026-8763 Référence CVE CVE-2026-87910 https://www.cve.org/CVERecord?id=CVE-2026-87910 Référence CVE CVE-2026-9076 https://www.cve.org/CVERecord?id=CVE-2026-9076 Référence CVE CVE-2026-91776 https://www.cve.org/CVERecord?id=CVE-2026-91776 Référence CVE CVE-2026-91777 https://www.cve.org/CVERecord?id=CVE-2026-91777 Référence CVE CVE-2026-9547 https://www.cve.org/CVERecord?id=CVE-2026-9547 Référence CVE CVE-2026-97687 https://www.cve.org/CVERecord?id=CVE-2026-97687 Référence CVE CVE-2026-97688 https://www.cve.org/CVERecord?id=CVE-2026-97688 Référence CVE CVE-2026-97689 https://www.cve.org/CVERecord?id=CVE-2026-97689 Gestion détaillée du document le 02 octobre 2026 Version initiale

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

De multiples vulnérabilités ont été découvertes dans Python. Certaines d'entre elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, une atteinte à l'intégrité des données et un contournement de la politique de sécurité.

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
Fixed
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
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 11 Sept 2026 · Last source change 3 Oct 2026, 00:33 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

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-09-13
European sourceENISA EUVD · EUVD-2026-76162
Product sourceVendor CSAF · SUSE Product Security Team
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-87910.
    Before
    remediation: access.redhat.com/CVE-2026-87910
    After
    no authoritative guidance recorded
    CNA ↗
  2. 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.0a1 < 3.15.0 · 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.15.0a1 < 3.15.0rc3 · 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. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2026-87910.
    Before
    remediation: access.redhat.com/CVE-2026-87910
    After
    no authoritative guidance recorded
    CNA ↗
  5. 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.0a1 < 3.15.0 · 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.0a1 < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  6. Vendor guidanceAuthoritative vendor guidance changed: removed patch: github.com/3105a3498aaf681ce128cf5baf83c2e5574267c5; removed patch: github.com/a4919937a4e1e69a0d178909c6f20557eca5d1d0; 1 further removals.
    Before
    patch: github.com/3105a3498aaf681ce128cf5baf83c2e5574267c5 · patch: github.com/a4919937a4e1e69a0d178909c6f20557eca5d1d0 · remediation: github.com/3105a3498aaf681ce128cf5baf83c2e5574267c5
    After
    no authoritative guidance recorded
    CNA ↗
  7. 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.0a1 < 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
    CPython: < 3.10.22, 3.11.0 < 3.11.17, 3.12.0 < 3.12.15, 3.13.0 < 3.13.16, 3.14.0a1 < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  8. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  9. Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/3105a3498aaf681ce128cf5baf83c2e5574267c5; added patch: github.com/a4919937a4e1e69a0d178909c6f20557eca5d1d0; removed remediation: access.redhat.com/CVE-2026-87910; 1 further additions.
    Before
    remediation: access.redhat.com/CVE-2026-87910
    After
    patch: github.com/3105a3498aaf681ce128cf5baf83c2e5574267c5 · patch: github.com/a4919937a4e1e69a0d178909c6f20557eca5d1d0 · remediation: github.com/3105a3498aaf681ce128cf5baf83c2e5574267c5
    github.com ↗
  10. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.12.15, 3.13.0 < 3.13.16, 3.14.0a1 < 3.15.0 · 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.0a1 < 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 ↗
  11. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2026-87910.
    Before
    remediation: access.redhat.com/CVE-2026-87910
    After
    no authoritative guidance recorded
    CNA ↗
  12. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.12.15, 3.13.0 < 3.13.16, 3.14.0a1 < 3.15.0 · 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.0a1 < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  13. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  14. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.12.15, 3.13.0 < 3.13.16, 3.14.0a1 < 3.15.0 · 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.0a1 < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  15. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2026-87910.
    Before
    remediation: access.redhat.com/CVE-2026-87910
    After
    no authoritative guidance recorded
    CNA ↗
  16. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.15.0 · 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.0a1 < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  17. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  18. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2026-87910.
    Before
    remediation: access.redhat.com/CVE-2026-87910
    After
    no authoritative guidance recorded
    CNA ↗
  19. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.15.0 · 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.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  20. Vendor guidanceAuthoritative vendor guidance changed: removed patch: github.com/764fd0af8d9e19d3684a58d2e58bf770f0605036; removed remediation: github.com/764fd0af8d9e19d3684a58d2e58bf770f0605036.
    Before
    patch: github.com/764fd0af8d9e19d3684a58d2e58bf770f0605036 · remediation: github.com/764fd0af8d9e19d3684a58d2e58bf770f0605036
    After
    no authoritative guidance recorded
    CNA ↗
  21. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 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
    CPython: < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  22. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  23. Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/764fd0af8d9e19d3684a58d2e58bf770f0605036; added remediation: github.com/764fd0af8d9e19d3684a58d2e58bf770f0605036; removed remediation: access.redhat.com/CVE-2026-87910.
    Before
    remediation: access.redhat.com/CVE-2026-87910
    After
    patch: github.com/764fd0af8d9e19d3684a58d2e58bf770f0605036 · remediation: github.com/764fd0af8d9e19d3684a58d2e58bf770f0605036
    github.com ↗
  24. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.15.0 · 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.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 ↗
  25. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/CVE-2026-87910.
    Before
    remediation: access.redhat.com/CVE-2026-87910
    After
    no authoritative guidance recorded
    CNA ↗
  26. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.15.0 · 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.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  27. Vendor guidanceAuthoritative vendor guidance changed: removed patch: github.com/9c17bace90f88dfba6d0e2fe23c8e7ae35f83955; removed remediation: github.com/9c17bace90f88dfba6d0e2fe23c8e7ae35f83955.
    Before
    patch: github.com/9c17bace90f88dfba6d0e2fe23c8e7ae35f83955 · remediation: github.com/9c17bace90f88dfba6d0e2fe23c8e7ae35f83955
    After
    no authoritative guidance recorded
    CNA ↗
  28. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 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
    CPython: < 3.15.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  29. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
  30. Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/9c17bace90f88dfba6d0e2fe23c8e7ae35f83955; added remediation: github.com/9c17bace90f88dfba6d0e2fe23c8e7ae35f83955; removed remediation: access.redhat.com/CVE-2026-87910.
    Before
    remediation: access.redhat.com/CVE-2026-87910
    After
    patch: github.com/9c17bace90f88dfba6d0e2fe23c8e7ae35f83955 · remediation: github.com/9c17bace90f88dfba6d0e2fe23c8e7ae35f83955
    github.com ↗
  31. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.15.0 · 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.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 ↗
  32. 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.15.0a1 < 3.15.0rc3 · 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.15.0a1 < 3.15.0rc3 · 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 ↗
  33. 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.0a1 < 3.15.0 · 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.0a1 < 3.15.0 · 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 ↗
  34. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.12.15, 3.13.0 < 3.13.16, 3.14.0a1 < 3.15.0 · 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.0a1 < 3.15.0 · 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 ↗
  35. 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.0 · 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 ↗
  36. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-87910 to remediation: access.redhat.com/CVE-2026-87910.
    Before
    remediation: access.redhat.com/CVE-2026-87910
    After
    remediation: access.redhat.com/CVE-2026-87910
    Red Hat Product Security ↗
  37. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  38. 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: python-unversioned-command-0:3.14.7-1.2.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; python-unversioned-command-0:3.14.7-1.2.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images; python3-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3-debug-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3-debug-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3-devel-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3-devel-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3-idle-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3-idle-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3-libs-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3-libs-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3-test-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3-test-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3-tkinter-0:3.14.7-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3-tkinter-0:3.14.7-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3.10-0:3.10.21-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3.10-0:3.10.21-1.2.hum1@src as a component of Red Hat Hardened Images; python3.10-0:3.10.21-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3.10-debug-0:3.10.21-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3.10-debug-0:3.10.21-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3.10-devel-0:3.10.21-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3.10-devel-0:3.10.21-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3.10-idle-0:3.10.21-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3.10-idle-0:3.10.21-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3.10-libs-0:3.10.21-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3.10-libs-0:3.10.21-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3.10-test-0:3.10.21-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; python3.10-test-0:3.10.21-1.2.hum1@x86_64 as a component of Red Hat Hardened Images; python3.10-tkinter-0:3.10.21-1.2.hum1@aarch64 as a component of Red Hat Hardened Images; and 65 more
    Red Hat Product Security ↗
  39. ENISA EUVD mappingEUVD-2026-76162 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-76162"}
    ENISA EUVD ↗
  40. Affected versionsThe structured affected or fixed version information changed.
    Before
    CPython: < 3.16.0 · 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 ↗
  41. 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-76162↗Vendor CSAF · SUSE Product Security Team↗Red Hat Product Security security advisory↗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-87910 · cve.blacktree.nl