CVE-2026-85091
Received Received - Intake

Heap Buffer Overflow in zlib gz_vacate() Function

Vulnerability report for CVE-2026-85091, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-03

Last updated on: 2026-09-03

Assigner: VulnCheck

Description

zlib versions 1.3.1.2 through 1.3.2 contain a heap buffer overflow vulnerability in the gz_vacate() function when processing non-blocking gzwrite() operations with stale external buffer pointers. Attackers can trigger the overflow by calling gzprintf() or gzvprintf() after a write stall, causing an unchecked memmove() to write beyond the internal input buffer boundary.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-03
Last Modified
2026-09-03
Generated
2026-09-03
AI Q&A
2026-09-03
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
madler zlib From 1.3.1.2 (inc) to 1.3.2 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-85091 is a heap buffer overflow in zlib versions 1.3.1.2 through 1.3.2 affecting the gz_vacate() function. It occurs during non-blocking gzwrite() operations when stale external buffer pointers are present. Attackers exploit this by calling gzprintf() or gzvprintf() after a write stall, causing an unchecked memmove() to write beyond the internal input buffer boundary.

Detection Guidance

To detect this vulnerability, check your zlib version with 'zlib-config --version' or 'dpkg -l | grep zlib'. If using 1.3.1.2 through 1.3.2, the system is vulnerable. Monitor applications using gzprintf() or gzvprintf() with non-blocking writes for crashes or memory corruption.

Impact Analysis

This vulnerability can lead to crashes, data corruption, or potentially arbitrary code execution if heap memory is overwritten. It requires specific conditions like non-blocking file descriptors and large writes followed by gzprintf() calls. The impact depends on the application's heap layout and memory allocator.

Mitigation Strategies

Upgrade zlib to a patched version immediately. If upgrading is not possible, disable non-blocking gzip writes in applications or avoid using gzprintf() and gzvprintf() after write stalls. Apply strict input validation for gzip operations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-85091. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart