← Übersicht Red Hat Enterprise Linux

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

CVE-2026-39244 · CLSA-2026-1784856024 · CLSA-2026-1790161376 · CLSA-2026-1790162696 · CLSA-2026-1790165044 · CLSA-2026-1790176614 · CLSA-2026-1791315520 · GHSA-xcpc-8h2w-3j85

Hoch · CVSS 7.5 SUSE: importantRed Hat: Moderate Netzwerk · ohne Login Kein Fix bekannt

Veröffentlicht
10.07.2026
Zuletzt geändert
15.10.2026
EPSS (30 Tage)
0.8 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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.

Status beim Hersteller

SUSE stuft seine Produktlinien ein: 7 betroffen, 1 behoben, 14 nicht betroffen.

Red Hat Advanced Cluster Management for Kubernetes 2 BetroffenFix zurückgestellt rhacm2/volsync-operator-bundle, rhacm2/volsync-rhel9
Red Hat Build of Podman Desktop BetroffenFix zurückgestellt rh-podman-desktop.git
Red Hat Developer Hub 1 BetroffenFix zurückgestellt rhdh/rhdh-hub-rhel9
Red Hat Enterprise Linux 8 BetroffenFix zurückgestellt dotnet5.0-build-reference-packages, mozjs60, mozjs60-devel
Red Hat Enterprise Linux 9 BetroffenFix zurückgestellt gjs, gjs-devel
Red Hat OpenShift AI (RHOAI) BetroffenFix zurückgestellt rhoai/odh-dashboard-rhel9, rhoai/odh-mlflow-rhel9, rhoai/odh-mod-arch-automl-rhel9, rhoai/odh-mod-arch-autorag-rhel9, rhoai/odh-mod-arch-eval-hub-rhel9, rhoai/odh-mod-arch-gen-ai-rhel9, rhoai/odh-mod-arch-maas-rhel9, rhoai/odh-mod-arch-mlflow-rhel9, rhoai/odh-mod-arch-model-registry-rhel9
Self-service automation portal 2 BetroffenFix zurückgestellt ansible-automation-platform/automation-portal
Cluster Observability Operator 1.5 Behoben cluster-observability-operator/distributed-tracing-console-plugin-pf4-rhel9, cluster-observability-operator/distributed-tracing-console-plugin-pf5-rhel9, cluster-observability-operator/distributed-tracing-console-plugin-pf6-rhel9 RHSA-2026:74609
Nicht betroffen (14)
Cluster Observability Operator 1.5Nicht betroffenverwundbarer Code nicht enthaltencluster-observability-operator/alertmanager-rhel9, cluster-observability-operator/cluster-health-analyzer-rhel9, cluster-observability-operator/cluster-observability-operator-bundle, cluster-observability-operator/cluster-observability-rhel9-operator, cluster-observability-operator/dashboards-console-plugin-rhel9, cluster-observability-operator/distributed-tracing-console-plugin-rhel9, cluster-observability-operator/korrel8r-rhel9, cluster-observability-operator/logging-console-plugin-pf4-rhel9, cluster-observability-operator/logging-console-plugin-pf5-rhel9, cluster-observability-operator/logging-console-plugin-rhel9, cluster-observability-operator/monitoring-console-plugin-pf5-rhel9, cluster-observability-operator/monitoring-console-plugin-pf6-rhel9, cluster-observability-operator/monitoring-console-plugin-rhel9, cluster-observability-operator/obo-prometheus-operator-admission-webhook-rhel9, cluster-observability-operator/obo-prometheus-operator-prometheus-config-reloader-rhel9, cluster-observability-operator/obo-prometheus-rhel9-operator, cluster-observability-operator/perses-rhel9, cluster-observability-operator/perses-rhel9-operator, cluster-observability-operator/prometheus-rhel9, cluster-observability-operator/thanos-rhel9, cluster-observability-operator/troubleshooting-panel-console-plugin-pf6-rhel9, cluster-observability-operator/troubleshooting-panel-console-plugin-rhel9
Red Hat OpenShift Container Platform 4Nicht betroffenverwundbarer Code wird nicht ausgeführtopenshift4/ose-console, openshift4/ose-monitoring-plugin-rhel9
Red Hat OpenShift Container Platform 5Nicht betroffenverwundbarer Code wird nicht ausgeführtopenshift5/ose-monitoring-plugin-rhel9
SUSE Linux Enterprise Micro 5.3Nicht betroffencockpit, cockpit-bridge, cockpit-machines, cockpit-networkmanager, cockpit-selinux, cockpit-storaged, cockpit-system, cockpit-ws
SUSE Linux Enterprise Micro 5.4Nicht betroffencockpit, cockpit-bridge, cockpit-machines, cockpit-networkmanager, cockpit-selinux, cockpit-storaged, cockpit-system, cockpit-ws
SUSE Linux Enterprise Micro 5.5Nicht betroffencockpit, cockpit-bridge, cockpit-machines, cockpit-networkmanager, cockpit-selinux, cockpit-storaged, cockpit-system, cockpit-ws
SUSE Linux Enterprise Server 16.0Nicht betroffencockpit, cockpit-bridge, cockpit-devel, cockpit-doc, cockpit-firewalld, cockpit-kdump, cockpit-machines, cockpit-networkmanager, cockpit-packagekit, cockpit-selinux, cockpit-storaged, cockpit-system, cockpit-ws, cockpit-ws-selinux
SUSE Linux Enterprise Server 16.1Nicht betroffencockpit, cockpit-bridge, cockpit-devel, cockpit-doc, cockpit-firewalld, cockpit-kdump, cockpit-machines, cockpit-networkmanager, cockpit-packagekit, cockpit-selinux, cockpit-storaged, cockpit-system, cockpit-ws, cockpit-ws-selinux
SUSE Linux Enterprise Server for SAP applications 16.0Nicht betroffencockpit, cockpit-bridge, cockpit-devel, cockpit-doc, cockpit-firewalld, cockpit-kdump, cockpit-machines, cockpit-networkmanager, cockpit-packagekit, cockpit-selinux, cockpit-storaged, cockpit-system, cockpit-ws, cockpit-ws-selinux
SUSE Linux Enterprise Server for SAP applications 16.1Nicht betroffencockpit, cockpit-bridge, cockpit-devel, cockpit-doc, cockpit-firewalld, cockpit-kdump, cockpit-machines, cockpit-networkmanager, cockpit-packagekit, cockpit-selinux, cockpit-storaged, cockpit-system, cockpit-ws, cockpit-ws-selinux
SUSE Linux Micro 6.0Nicht betroffencockpit, cockpit-bridge, cockpit-machines, cockpit-networkmanager, cockpit-selinux, cockpit-storaged, cockpit-system, cockpit-ws
SUSE Linux Micro 6.1Nicht betroffencockpit, cockpit-bridge, cockpit-machines, cockpit-networkmanager, cockpit-selinux, cockpit-storaged, cockpit-system, cockpit-ws
SUSE Linux Micro 6.2Nicht betroffencockpit, cockpit-bridge, cockpit-firewalld, cockpit-kdump, cockpit-machines, cockpit-networkmanager, cockpit-selinux, cockpit-storaged, cockpit-system, cockpit-ws, cockpit-ws-selinux
openSUSE Leap 16.0Nicht betroffencockpit, cockpit-machines

Betroffene Pakete im beobachteten Stack

Red Hat:enterprise_linux:8dotnet5.0-build-reference-packageskein Fix bekanntCVE-2026-39244
Red Hat:enterprise_linux:8mozjs60kein Fix bekanntCVE-2026-39244
Red Hat:enterprise_linux:8mozjs60-develkein Fix bekanntCVE-2026-39244
Red Hat:enterprise_linux:9gjskein Fix bekanntCVE-2026-39244
Red Hat:enterprise_linux:9gjs-develkein Fix bekanntCVE-2026-39244
Weitere betroffene Pakete (8)
TuxCare:npmadm-zip0.4.16-tuxcare.0 → 0.4.16-tuxcare.1CLSA-2026-1784769498
TuxCare:npmadm-zip0.5.18-tuxcare.0 → 0.5.18-tuxcare.1CLSA-2026-1784856024
TuxCare:npmadm-zip0.5.17-tuxcare.0 → 0.5.17-tuxcare.1CLSA-2026-1790161376
TuxCare:npmadm-zip0.5.16-tuxcare.0 → 0.5.16-tuxcare.1CLSA-2026-1790162696
TuxCare:npmadm-zip0.5.12-tuxcare.0 → 0.5.12-tuxcare.1CLSA-2026-1790165044
TuxCare:npmadm-zip0.5.10-tuxcare.0 → 0.5.10-tuxcare.1CLSA-2026-1790176614
TuxCare:npmadm-zip0.4.7-tuxcare.0 → 0.4.7-tuxcare.2CLSA-2026-1791315520
npmadm-zip0.6.0GHSA-xcpc-8h2w-3j85

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.