Skip to content
VulniPulse
Advisory severityMedium6.5Red Hat Linux

Medium [CVE-2026-39244] Denial of Service via crafted ZIP file leading to excessive memory allocation

This medium-severity Red Hat Linux advisory covers CVE-2026-39244 affecting Cluster Observability Operator 1.5.3, Red Hat Advanced Cluster Management for Kubernetes 2, Red Hat Build of Podman Desktop.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-39244 Source published Source updated

VulniPulse record published Record updated

CVE-2026-39244
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Summary

adm-zip before 0.5.18 is vulnerable to denial of service via a crafted ZIP file with a manipulated uncompressed size header field.

In zipEntry.js line 103, Buffer.alloc(_centralHeader.size) allocates memory based on the declared uncompressed size from the ZIP central directory header without validating it against the actual compressed data size or imposing any upper bound. The size value is read directly from the binary header at entryHeader.js line 266 with no bounds check.

An attacker can craft a ~120-byte ZIP file that declares ~4GB uncompressed size, causing a memory allocation amplification ratio of over 33 million to 1. The allocation occurs before CRC validation, so the malicious payload cannot be rejected early.

All extraction and read methods are affected: readFile(), readAsText(), extractEntryTo(), extractAllTo(), extractAllToAsync(), test(), and entry.getData(). Any application accepting untrusted ZIP files via adm-zip is vulnerable to immediate process crash.

A remote attacker can exploit this vulnerability by providing a specially crafted ZIP file. The file's header can be manipulated to declare an extremely large uncompressed size, causing the application to allocate an excessive amount of memory.

A denial of service flaw exists in adm-zip, affecting applications that process untrusted ZIP archives.

Is CVE-2026-39244 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-39244 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-39244?

Upgrade to a fixed release named by Red Hat:

  • cluster-observability-operator/distributed-tracing-console-plugin-pf4-rhel9:1790854545
  • cluster-observability-operator/distributed-tracing-console-plugin-pf5-rhel9:1790854478
  • cluster-observability-operator/distributed-tracing-console-plugin-pf6-rhel9:1790854538
  • RHSA-2026:74609

Confirm against the vendor advisory before you patch.

Affected versions
  • < 0.5.18

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Fixed versions
  • cluster-observability-operator/distributed-tracing-console-plugin-pf4-rhel9:1790854545
  • cluster-observability-operator/distributed-tracing-console-plugin-pf5-rhel9:1790854478
  • cluster-observability-operator/distributed-tracing-console-plugin-pf6-rhel9:1790854538
  • RHSA-2026:74609

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Get an email when Red Hat RHEL & SELinux publishes the next one.

See Red Hat RHEL & SELinux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat RHEL & SELinux
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.