Skip to content

CVE-2026-6100 on CTRL-OS 26.05

Aliases: CVE-2026-6100

Packages: python313

Status: Plausible, Resolved

Advisory Information

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.

Updates

2026-07-23 16:21 CEST

Metadata changes:

  • Status for package python313: “Resolved” (fff38d56fb8e15a140da141149c596766b838d0b)

2026-07-23 16:21 CEST

Metadata changes:

  • Status for package python314: “Resolved” (8720e26a455838194d661c3d1e8e9f0c2de4ba94)

2026-07-23 16:21 CEST

Metadata changes:

  • Status for package python315: “Resolved” (de92bac9084b9249b02934240202bf9d74a3a9c3)

2026-07-23 16:21 CEST

Metadata changes:

  • Status for package python311: “Plausible”
  • Status for package python312: “Plausible”
  • Status for package python313: “Plausible”
  • Status for package python314: “Plausible”
  • Status for package python315: “Plausible”

2026-06-01 17:44 CEST

Metadata changes:

  • Status for package python311: “New”
  • Status for package python312: “New”
  • Status for package python313: “New”
  • Status for package python314: “New”
  • Status for package python315: “New”

(Amended on: 2026-06-01 17:45 CEST)