Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-74764 – Path Traversal / Arbitrary File Write (RCE potential) – Pandora (pandora-analysis)

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-74764 is a critical path traversal vulnerability in Pandora, the file-analysis framework maintained by pandora-analysis (CIRCL). The flaw exists in Pandora’s TAR archive extraction functionality, which fails to sanitize member names before extracting them to disk, allowing crafted archive entries to be written outside the intended extraction directory. The issue affects all Pandora versions from the beginning of the project through 1.12.5 and has been assigned a maximum CVSS score of 10.0.

Technical details

  • Root cause: Pandora’s extractor worker (pandora/workers/extractor.py) calls Python’s tarfile.TarFile.extract() on submitted TAR archive members without applying a safe extraction filter, so member paths containing ../ sequences or absolute paths are extracted as-is.
  • Trigger condition: An attacker submits a specially crafted TAR archive (e.g., via Pandora’s file submission/analysis workflow) containing archive entries with malicious relative or absolute paths.
  • Attack vector: Network — no authentication or user interaction beyond submitting a file for analysis is required to trigger extraction.
  • Impact: Files extracted from the malicious archive can be written outside the designated extraction directory, potentially overwriting sensitive files, planting files in locations that lead to code execution, or causing denial of service. CVSS impact metrics rate confidentiality, integrity, and availability impact as High.

Affected software

  • Product: Pandora (pandora-analysis)
  • Repository: pandora-analysis/pandora
  • Affected versions: All versions from initial release through 1.12.5 (inclusive)

Severity

  • CVSS v4.0 Base Score: 10.0 (Critical)
  • Vector: 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
  • CWE: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / Path Traversal)

Mitigation and recommended actions

  • Immediate: Upgrade Pandora to a version that includes the fix applied in commit 186b58d41e04248a154d274fffb5813e7fa2012e, which adds filter='data' to the tar.extract() call in extractor.py, causing dangerous TAR members (path traversal entries, device files, etc.) to be rejected during extraction. Confirm the deployed version is newer than 1.12.5 and includes this patch.
  • If unable to patch immediately:
    • Restrict or disable the TAR/archive extraction worker in Pandora deployments that do not require archive analysis.
    • Run Pandora’s analysis workers with minimal filesystem privileges and in an isolated/containerized environment so that any unintended file writes cannot affect the host system or other services.
    • Monitor extraction directories and worker logs for unexpected files written outside expected analysis output paths.
    • Restrict network exposure of the Pandora submission interface to trusted users/networks until patched.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge