Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-74764Published 2026-08-15

CVE-2026-74764 — pandora-analysis pandora

critical (derived)

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

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

Last updated:

What is CVE-2026-74764?

Pandora contains a path traversal vulnerability in its TAR archive extraction functionality. When processing a submitted TAR archive, the extractor passed archive member names directly to Python's tarfile.TarFile.extract() without applying an extraction filter. An attacker able to submit a specially crafted TAR archive containing malicious member paths, such as paths using ../ sequences or absolute paths, could cause extracted files to be written outside the intended extraction directory. This may allow the attacker to overwrite files accessible to the Pandora worker process and could potentially result in application compromise, arbitrary code execution, or denial of service depending on the files targeted and the privileges of the Pandora process. The vulnerability is corrected by using Python's filter='data' extraction filter, which rejects or sanitizes dangerous TAR members, including paths that escape the destination directory and unsafe link targets. The weakness corresponds to MITRE's general path traversal category, which includes archive extraction cases where attacker-controlled filenames cause files to be written outside the intended directory.

The record classifies CVE-2026-74764 under weakness class CWE-22. 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
10 — Critical (derived from score)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L
EPSS (FIRST)
0.4% probability of exploitation in the next 30 days, higher than 33.7% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
6.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-08-15

Is CVE-2026-74764 being exploited?

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

Affected products and versions

  • pandora-analysis: pandora

How to fix CVE-2026-74764

No vendor patch reference has been recorded for CVE-2026-74764 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-74764

No threat campaign in the Threadlinqs corpus currently references CVE-2026-74764, 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