Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-74767Published 2026-08-15

CVE-2026-74767 — pandora-analysis pandora

high (derived)

As of 2026-08-15, CVE-2026-74767 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in pandora-analysis pandora, CVSS v4.0 8.7, EPSS 0.2% (17.0th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-74767 as of 2026-08-15; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
8.7/10High (derived)
EPSS
0.2%Higher than 17.0% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
5/10Threadlinqs triage score
Published
CVSS v4.0 8.7 (High, derived from score) · EPSS 0.2% (higher than 17.0% of all scored CVEs) · Priority 5/10 · Published 2026-08-15

Last updated:

What is CVE-2026-74767?

Pandora contains a denial-of-service vulnerability in its handling of DAA (Direct Access Archive) files. When extracting the internal ISO image from a DAA archive, compressed chunks were decompressed using zlib.decompress() without enforcing a limit on the resulting uncompressed data. An attacker able to submit a crafted DAA file containing highly compressed data could cause Pandora to decompress a relatively small input into a very large amount of data in memory. Because the decompressed chunks are accumulated to construct the internal ISO image, this could result in excessive memory consumption and potentially CPU exhaustion, causing the extraction worker to become unresponsive, terminate, or affect the availability of the Pandora service. The patch introduces bounded decompression using decompressobj().decompress() with max_extracted_filesize, verifies the cumulative size of decompressed chunks, and raises a dedicated ZipBomb exception when the configured limit is exceeded. Pandora then aborts extraction and reports the file as too large.

The record classifies CVE-2026-74767 under weakness class CWE-434. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 51 days ago.

Severity and exploitation probability

CVSS v4.0 base score
8.7 — High (derived from score)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L
EPSS (FIRST)
0.2% probability of exploitation in the next 30 days, higher than 17.0% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-08-15

Is CVE-2026-74767 being exploited?

It currently carries a trending score of 34 in the Threadlinqs vulnerability feed.

Affected products and versions

  • pandora-analysis: pandora

How to fix CVE-2026-74767

No vendor patch reference has been recorded for CVE-2026-74767 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-74767

No threat campaign in the Threadlinqs corpus currently references CVE-2026-74767, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on .

Vendor advisory and patch