CVE-2026-74764: Path Traversal in TAR Archive Extraction Allows Arbitrary File Write in Pandora
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.
Security readout for executives and security teams
Plain-English summary
Pandora can unpack attacker-supplied TAR files outside its intended folder. A remote, unauthenticated attacker could overwrite files available to the worker process, potentially disrupting service or compromising the application. Impact depends on Pandora’s permissions and which files can be replaced.
Executive priority
Prioritize immediate validation and remediation for internet-facing or broadly accessible Pandora deployments. The potential impact spans confidentiality, integrity, availability, and downstream systems, although real-world exploitation is not established. Escalate fastest where the worker can modify application code, configuration, credentials, or startup files.
Technical view
Archive member names were passed directly to Python’s tarfile.TarFile.extract() without an extraction filter. Parent-directory paths, absolute paths, or unsafe link targets could escape the destination directory. The cited patch applies filter='data', which rejects or sanitizes dangerous members. The record assigns CVSS 4.0 score 10.0 and CWE-22.
Likely exposure
Exposure is most likely where Pandora accepts TAR submissions from untrusted users and runs the vulnerable extraction code. Network reachability and unnecessary worker filesystem privileges increase risk. The supplied affected-version data lists version “0” and defaults others to unaffected, so exact release coverage is unclear and should be verified against deployed code.
Exploitation context
The CVSS vector describes network-accessible, low-complexity, unauthenticated exploitation requiring no user interaction. However, the supplied record is not in KEV and provides no evidence of exploitation in the wild. Treat exploitation status as unconfirmed, not absent.
Researcher notes
The vulnerability is a TAR path-traversal arbitrary-file-write condition rather than demonstrated code execution. Code execution and full compromise depend on writable targets and process privileges. The patch mechanism is clearly identified, but the supplied version metadata is unusually narrow and insufficient to map all releases confidently.
Mitigation direction
Apply the vendor patch that enables Python’s filter='data' during TAR extraction.
Confirm deployed builds include commit 186b58d41e04248a154d274fffb5813e7fa2012e or equivalent vendor guidance.
Restrict untrusted archive submissions until patched where operationally feasible.
Run Pandora workers with minimal filesystem permissions to reduce overwrite impact.
Review worker-accessible files for unexpected changes if hostile archives may have been processed.
Validation and detection
Inspect the deployed extraction path and confirm every TAR extraction uses filter='data' or an equivalent safe filter.
Run safe regression tests confirming parent-relative, absolute, and unsafe-link archive members are rejected.
Verify ordinary TAR archives still extract only within the intended destination.
Compare deployed source or package provenance with the cited patch and vendor release guidance.
Review relevant extraction logs and worker-accessible files for suspicious writes outside expected directories.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory
Improper Limitation of a Pathname to a Restricted Directory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.