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

Use-after-free in lzma.LZMADecompressor, bz2.BZ2Decompressor, and gzip.GzipFile after re-use under memory pressure

Python Software Foundation · CPython

9.1CriticalCVSS 4.0
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.76% 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: Within 3 daysRemediation target: Within 90 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.

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.

15 package states
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.14-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.14-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.14-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcepypy3Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian trixietrixie · sourcepython3.13Vendor fix publishedDebian records a fixed source-package version for this release.3.13.5-2+deb13u2Debian 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.11Vendor fix publishedDebian records a fixed source-package version for this release.3.11.2-6+deb12u8Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepypy3Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython3.13Vendor fix publishedDebian records a fixed source-package version for this release.3.13.14-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython3.14Vendor fix publishedDebian records a fixed source-package version for this release.3.14.5~rc1-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepypy3Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython3.13Vendor fix publishedDebian records a fixed source-package version for this release.3.13.14-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython3.14Vendor fix publishedDebian records a fixed source-package version for this release.3.14.5~rc1-1Debian 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.12Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.3.12.3-1ubuntu0.15Canonical 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-6100 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypython: Python: Arbitrary code execution or information disclosure via use-after-free in decompression modules
19 known affected

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

  • python as a component of Red Hat Enterprise Linux 6
  • python-devel as a component of Red Hat Enterprise Linux 6
  • python-libs as a component of Red Hat Enterprise Linux 6
  • python-test as a component of Red Hat Enterprise Linux 6
  • python-tools as a component of Red Hat Enterprise Linux 6
  • python.src as a component of Red Hat Enterprise Linux 6
  • tkinter as a component of Red Hat Enterprise Linux 6
  • python as a component of Red Hat Enterprise Linux 7
  • python-debug as a component of Red Hat Enterprise Linux 7
  • python-devel as a component of Red Hat Enterprise Linux 7
  • python-libs as a component of Red Hat Enterprise Linux 7
  • python-test as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in Python's decompression modules, including `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile`. This vulnerability, a use-after-free, can occur if a program attempts to re-use a decompression object after a memory allocation error, especially when the system is experiencing high memory usage. Exploitation of this flaw could potentially allow an attacker to execute arbitrary code or access sensitive data. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
CVE-2026-6100 · CSAF 2.0 · revision 1 · finalStackable Product Security TeamStackable Security Advisory for: CVE-2026-6100
10 fixed

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

  • pkg:rpm/redhat/python3.11-libs@3.11.13-5.1.el9_7?arch=aarch64&distro=redhat-9.7@pkg:oci/spark-k8s@sha256%3A7bf0d1eae3e6a880bef9b8ea73091e496f359c79ee351c51202514608965113f?arch=arm64&repository_url=oci.stackable.tech%2Fsdp%2Fspark-k8s
  • pkg:rpm/redhat/python3.11@3.11.13-5.1.el9_7?arch=aarch64&distro=redhat-9.7@pkg:oci/spark-k8s@sha256%3A7bf0d1eae3e6a880bef9b8ea73091e496f359c79ee351c51202514608965113f?arch=arm64&repository_url=oci.stackable.tech%2Fsdp%2Fspark-k8s
  • pkg:rpm/redhat/python3.12-libs@3.12.12-4.el9_7.1?arch=aarch64&distro=redhat-9.7@pkg:oci/spark-k8s@sha256%3A3cb08c61b6253cf44c2f3c41d503df1b28380e65d79435e7fbd22883fcf24e5e?arch=arm64&repository_url=oci.stackable.tech%2Fsdp%2Fspark-k8s
  • pkg:rpm/redhat/python3.12@3.12.12-4.el9_7.1?arch=aarch64&distro=redhat-9.7@pkg:oci/spark-k8s@sha256%3A3cb08c61b6253cf44c2f3c41d503df1b28380e65d79435e7fbd22883fcf24e5e?arch=arm64&repository_url=oci.stackable.tech%2Fsdp%2Fspark-k8s
  • pkg:rpm/redhat/python3.12-libs@3.12.12-4.el9_7.1?arch=aarch64&distro=redhat-9.7@pkg:oci/spark-k8s@sha256%3A0d0cb3e70ddaae3d102e48c3549b7d075216302a05a11f64a8dd5330add59f11?arch=arm64&repository_url=oci.stackable.tech%2Fsdp%2Fspark-k8s
  • pkg:rpm/redhat/python3.12@3.12.12-4.el9_7.1?arch=aarch64&distro=redhat-9.7@pkg:oci/spark-k8s@sha256%3A0d0cb3e70ddaae3d102e48c3549b7d075216302a05a11f64a8dd5330add59f11?arch=arm64&repository_url=oci.stackable.tech%2Fsdp%2Fspark-k8s
  • pkg:rpm/redhat/python3-libs@3.9.25-3.el9_7.1?arch=aarch64&distro=redhat-9.7@pkg:oci/superset@sha256%3A6afd2d46098fbb06cdaa03407370e4098f853bccf80b71bef12bee67a534e3b3?arch=arm64&repository_url=oci.stackable.tech%2Fsdp%2Fsuperset
  • pkg:rpm/redhat/python3@3.9.25-3.el9_7.1?arch=aarch64&distro=redhat-9.7@pkg:oci/superset@sha256%3A6afd2d46098fbb06cdaa03407370e4098f853bccf80b71bef12bee67a534e3b3?arch=arm64&repository_url=oci.stackable.tech%2Fsdp%2Fsuperset
  • pkg:rpm/redhat/python3.11-libs@3.11.13-5.1.el9_7?arch=aarch64&distro=redhat-9.7@pkg:oci/superset@sha256%3A998275a8dc141e9fa8e6e4a213f30f231f4d0ad23bd485bfa8ac3c11c8738369?arch=arm64&repository_url=oci.stackable.tech%2Fsdp%2Fsuperset
  • pkg:rpm/redhat/python3.11@3.11.13-5.1.el9_7?arch=aarch64&distro=redhat-9.7@pkg:oci/superset@sha256%3A998275a8dc141e9fa8e6e4a213f30f231f4d0ad23bd485bfa8ac3c11c8738369?arch=arm64&repository_url=oci.stackable.tech%2Fsdp%2Fsuperset
Summary
A flaw was found in Python's decompression modules, including `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile`. This vulnerability, a use-after-free, can occur if a program attempts to re-use a decompression object after a memory allocation error, especially when the system is experiencing high memory usage. Exploitation of this flaw could potentially allow an attacker to execute arbitrary code or access sensitive data. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.
Remediation
No remediation text is recorded.
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-22028

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

Use-after-free (UAF) was possible in the `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile` when a memory allocation fails with a `MemoryError` and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The fix cleans up the dangling pointer in this specific error condition. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.

What

Use-after-free (UAF) was possible in the `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile` when a memory allocation fails with a `MemoryError` and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The fix cleans up the dangling pointer in this specific error condition. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Use-after-free (UAF) was possible in the `lzma.LZMADecompressor`, `bz2.BZ2Decompressor`, and `gzip.GzipFile` when a memory allocation fails with a `MemoryError` and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The fix cleans up the dangling pointer in this specific error condition. The vulnerability is only present if the program re-uses decompressor instances across multiple decompression calls even after a `MemoryError` is raised during decompression. Using the helper functions to one-shot decompress data such as `lzma.decompress()`, `bz2.decompress()`, `gzip.decompress()`, and `zlib.decompress()` are not affected as a new decompressor instance is used per call. If the decompressor instance is not re-used after an error condition, this usage is similarly not vulnerable.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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 → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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:N/VC:H/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.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.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.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.
NetworkUnauthenticatedCWE-416
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2455Oracle Solaris Drittanbieterkomponenten: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in verschiedenen Komponenten von Drittanbietern in Oracle Solaris ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-1666IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-1087CPython: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Python ausnutzen, um Sicherheitsvorkehrungen zu umgehen, und um Daten zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260415Security Bulletin 15 April 2026

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

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

VERecord?id=CVE-2026-5598 Référence CVE CVE-2026-5758 https://www.cve.org/CVERecord?id=CVE-2026-5758 Référence CVE CVE-2026-5795 https://www.cve.org/CVERecord?id=CVE-2026-5795 Référence CVE CVE-2026-59869 https://www.cve.org/CVERecord?id=CVE-2026-59869 Référence CVE CVE-2026-59871 https://www.cve.org/CVERecord?id=CVE-2026-59871 Référence CVE CVE-2026-59873 https://www.cve.org/CVERecord?id=CVE-2026-59873 Référence CVE CVE-2026-59874 https://www.cve.org/CVERecord?id=CVE-2026-59874 Référence CVE CVE-2026-59875 https://www.cve.org/CVERecord?id=CVE-2026-59875 Référence CVE CVE-2026-6009 https://www.cve.org/CVERecord?id=CVE-2026-6009 Référence CVE CVE-2026-6100 https://www.cve.org/CVERecord?id=CVE-2026-6100 Référence CVE CVE-2026-6357 https://www.cve.org/CVERecord?id=CVE-2026-6357 Référence CVE CVE-2026-7769 https://www.cve.org/CVERecord?id=CVE-2026-7769 Référence CVE CVE-2026-8149 https://www.cve.org/CVERecord?id=CVE-2026-8149 Référence CVE CVE-2026-8286 https://www.cve.org/CVERecord?id=CVE-2026-8286 Référence CVE CVE-2026-8458 https://www.cve.org/CVERecord?id=CVE-2026-8458 Référence CVE CVE-2026-8723 https://www.cve.org/CVERecord?id=CVE-2026-8723 Référence CVE CVE-2026-8924 https://www.cve.org/CVERecord?id=CVE-2026-8924 Référence CVE CVE-2026-8927 https://www.cve.org/CVERecord?id=CVE-2026-8927 Ré

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

.cve.org/CVERecord?id=CVE-2026-4519 Référence CVE CVE-2026-4786 https://www.cve.org/CVERecord?id=CVE-2026-4786 Référence CVE CVE-2026-4800 https://www.cve.org/CVERecord?id=CVE-2026-4800 Référence CVE CVE-2026-4867 https://www.cve.org/CVERecord?id=CVE-2026-4867 Référence CVE CVE-2026-4923 https://www.cve.org/CVERecord?id=CVE-2026-4923 Référence CVE CVE-2026-4926 https://www.cve.org/CVERecord?id=CVE-2026-4926 Référence CVE CVE-2026-5121 https://www.cve.org/CVERecord?id=CVE-2026-5121 Référence CVE CVE-2026-5598 https://www.cve.org/CVERecord?id=CVE-2026-5598 Référence CVE CVE-2026-5795 https://www.cve.org/CVERecord?id=CVE-2026-5795 Référence CVE CVE-2026-6100 https://www.cve.org/CVERecord?id=CVE-2026-6100 Référence CVE CVE-2026-6918 https://www.cve.org/CVERecord?id=CVE-2026-6918 Référence CVE CVE-2026-8620 https://www.cve.org/CVERecord?id=CVE-2026-8620 Référence CVE CVE-2026-8633 https://www.cve.org/CVERecord?id=CVE-2026-8633 Gestion détaillée du document le 29 mai 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d

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

.cve.org/CVERecord?id=CVE-2026-4111 Référence CVE CVE-2026-4224 https://www.cve.org/CVERecord?id=CVE-2026-4224 Référence CVE CVE-2026-4424 https://www.cve.org/CVERecord?id=CVE-2026-4424 Référence CVE CVE-2026-4519 https://www.cve.org/CVERecord?id=CVE-2026-4519 Référence CVE CVE-2026-4539 https://www.cve.org/CVERecord?id=CVE-2026-4539 Référence CVE CVE-2026-4786 https://www.cve.org/CVERecord?id=CVE-2026-4786 Référence CVE CVE-2026-4878 https://www.cve.org/CVERecord?id=CVE-2026-4878 Référence CVE CVE-2026-5121 https://www.cve.org/CVERecord?id=CVE-2026-5121 Référence CVE CVE-2026-5598 https://www.cve.org/CVERecord?id=CVE-2026-5598 Référence CVE CVE-2026-6100 https://www.cve.org/CVERecord?id=CVE-2026-6100 Gestion détaillée du document le 11 mai 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

De multiples vulnérabilités ont été découvertes dans Python. Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance 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.
Patch available
Affected
Fixed
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
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 13 Apr 2026 · Last source change 13 Aug 2026, 00:27 UTC · CWE-416 · Use After Free

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-14
European sourceENISA EUVD · EUVD-2026-22028
Product sourceVendor CSAF · Red Hat Product Security
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. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 3.10.21; 3.11.0 < 3.11.16; 3.12.0 < 3.12.14; 3.13.0 < 3.13.14; 3.14.0a1 < 3.14.5rc1; 3.15.0a1 < 3.15.0b1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 3.10.21; 3.11.0 < 3.11.16; 3.12.0 < 3.12.14; 3.13.0 < 3.13.14; 3.14.0a1 < 3.14.5rc1; 3.15.0a1 < 3.15.0b1 · Fixed: Follow Stackable Product Security Team's fixed-release guidance in the linked advisory.
    Stackable Product Security Team ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Stackable Product Security Team ↗
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-22028↗Vendor CSAF · Red Hat Product Security↗Stackable Product Security Team 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-6100 · cve.blacktree.nl