Vulnerability · CVE-2026-6100
Use-after-free (UAF) was possible in the , , and when a memory allocation fails with a and the decompression instance is re-used.
Published Apr 13, 2026 · catalog updated Aug 13, 2026 · the affected product
Check if you run it
No confirmed exploitation is on record for CVE-2026-6100. EPSS is 0.76%. Act only if a listed version of the affected product is installed.
Gaps on this record
- No plain product name is stored. The page cannot tell you which product to check.
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Critical9.1
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.76%
- Remediation
- Not established
- Affected products
- See sources for product scope
Use-after-free (UAF) was possible in the , , and when a memory allocation fails with a 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 is raised during decompression. Using the helper functions to one-shot decompress data such as , , , and 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.
No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.
How to fix CVE-2026-6100
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-6100. EPSS is 0.76%. Act only if a listed version of the affected product is installed.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-416: Use After Free; CWE-787: Out-of-bounds Write; CWE-825. EPSS 0.76%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Apr 13, 2026 · NIST NVD
Detected
Use-after-free (UAF) was possible in the , , and when a memory allocation fails with a 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 afte
Aug 13, 2026 · NIST NVD
Updated
Use-after-free (UAF) was possible in the , , and when a memory allocation fails with a 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 afte
Sources
- CVE.orgVulnerability recordCVE-2026-6100
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-6100
30-day exploitation probability 0.8%
first.org - NIST NVDVulnerability recordCVE-2026-6100
Use-after-free (UAF) was possible in the , , and when a memory allocation fails with a and the decompression instance is re-used. This scenario can be triggered if the process is under memory pressure. The
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.