CVE-2026-74764

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 10.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
60(Track)
EG Risk 60/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (1)

Auto-updated Aug 17, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit 186b58d41e04 (pandora-analysis/pandora)

Patch available: pandora-analysis/pandora v1.12.6 (contains commit 186b58d41e04)

https://github.com/pandora-analysis/pandora/commit/186b58d41e04248a154d274fffb5813e7fa2012e

Vendor Advisories for CVE-2026-74764(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 51× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 05:09 UTCGHSA enrichment
  2. 2026-08-21 01:22 UTCEG score recompute
  3. 2026-08-21 01:22 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 21:36 UTCGHSA enrichment
  6. 2026-08-20 17:49 UTCGHSA enrichment
  7. 2026-08-20 14:02 UTCGHSA enrichment
  8. 2026-08-20 09:31 UTCGHSA enrichment
  9. 2026-08-20 05:45 UTCGHSA enrichment
  10. 2026-08-20 01:58 UTCGHSA enrichment
  11. 2026-08-19 22:11 UTCGHSA enrichment
  12. 2026-08-19 18:21 UTCEG score recompute
  13. 2026-08-19 18:21 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 14:22 UTCGHSA enrichment
  16. 2026-08-19 10:31 UTCGHSA enrichment
  17. 2026-08-19 06:44 UTCGHSA enrichment
  18. 2026-08-19 02:55 UTCGHSA enrichment
  19. 2026-08-18 23:08 UTCGHSA enrichment
  20. 2026-08-18 19:22 UTCGHSA enrichment
  21. 2026-08-18 15:35 UTCEG score recompute
  22. 2026-08-18 15:35 UTCGHSA enrichment
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 11:42 UTCGHSA enrichment
Show 26 more
  1. 2026-08-18 07:55 UTCGHSA enrichment
  2. 2026-08-18 04:08 UTCGHSA enrichment
  3. 2026-08-18 00:19 UTCGHSA enrichment
  4. 2026-08-17 20:30 UTCEG score recompute
  5. 2026-08-17 20:30 UTCGHSA enrichment
  6. 2026-08-17 19:50 UTCEG score recompute
  7. 2026-08-17 19:50 UTCGHSA enrichment
  8. 2026-08-17 16:03 UTCEG score recompute
  9. 2026-08-17 16:03 UTCGHSA enrichment
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 12:16 UTCGHSA enrichment
  12. 2026-08-17 08:29 UTCGHSA enrichment
  13. 2026-08-17 04:43 UTCGHSA enrichment
  14. 2026-08-17 00:56 UTCGHSA enrichment
  15. 2026-08-16 21:09 UTCGHSA enrichment
  16. 2026-08-16 17:22 UTCEG score recompute
  17. 2026-08-16 17:22 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 13:35 UTCGHSA enrichment
  21. 2026-08-16 09:48 UTCGHSA enrichment
  22. 2026-08-16 06:02 UTCGHSA enrichment
  23. 2026-08-16 02:15 UTCGHSA enrichment
  24. 2026-08-15 22:29 UTCEG score recompute
  25. 2026-08-15 21:53 UTCEG score recompute
  26. 2026-08-15 21:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74764?
CVE-2026-74764 is a critical vulnerability published on August 15, 2026. 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…
When was CVE-2026-74764 disclosed?
CVE-2026-74764 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74764 actively exploited?
CVE-2026-74764 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.1% of all scored CVEs.
What is the CVSS score of CVE-2026-74764?
CVE-2026-74764 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-74764?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74764, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74764

Explore →

Is Your Infrastructure Affected by CVE-2026-74764?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.