CVE-2026-6100 Affecting python-3.14 package, versions <3.14.5-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.52% (40th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-PYTHON314-17140300
  • published4 Jun 2026
  • disclosed13 Apr 2026

Introduced: 13 Apr 2026

CVE-2026-6100  (opens in a new tab)

How to fix?

Upgrade Minimos:latest python-3.14 to version 3.14.5-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-3.14 package and not the python-3.14 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1