CVE-2026-88069: Pandora Path Traversal Vulnerability

CVE-2026-88069 Overview

CVE-2026-88069 is a path traversal vulnerability [CWE-22] in Pandora, an open-source analysis platform maintained by pandora-analysis. The flaw resides in the archive extraction worker. When Pandora processes a crafted archive or disk image, attacker-controlled file paths are used without validating that the resulting destination stays within the intended extraction directory.

An attacker who can submit a malicious file for analysis can write extracted content outside the designated extraction directory. This can overwrite files accessible to the Pandora worker process, leading to unauthorized modification of application or system files, denial of service, and further compromise depending on process permissions.

Critical Impact
Remote, unauthenticated attackers can overwrite arbitrary files writable by the Pandora worker process by submitting a crafted archive for analysis.

Affected Products

Pandora analysis platform (pandora-analysis/pandora)
Versions prior to commit d86ac5b260fb9a41e07f1da1bbd326cdcfc188a7
Deployments using the archive extraction worker (pandora/workers/extractor.py)

Discovery Timeline

2026-09-09 - CVE-2026-88069 published to the National Vulnerability Database (NVD)
2026-09-09 - Last updated in NVD database

Technical Details for CVE-2026-88069

Vulnerability Analysis

Pandora accepts user-supplied files and dispatches them to worker modules for analysis. The archive extraction worker unpacks submitted archives and disk images into a working directory used by downstream analysis stages. The worker trusts filenames embedded inside the archive when constructing destination paths.

Because the destination path is built by joining the extraction directory with entry names from the archive, entries that contain traversal sequences such as ../ or absolute paths resolve outside the intended directory. The extractor writes the file to the resolved location without verifying containment.

The result is arbitrary file write with the privileges of the Pandora worker process. Depending on deployment, this can affect Pandora configuration files, analysis reports, cron files, or any other location the worker can write to.

Root Cause

The root cause is missing canonicalization and containment checks on archive entry paths before extraction. The worker did not resolve each destination path and confirm that it remained below the expected extraction directory, a well-known class of flaw commonly referred to as Zip Slip.

Attack Vector

Exploitation requires only the ability to submit a file for analysis. No authentication or user interaction is needed on network-exposed Pandora instances. The attacker crafts an archive whose entries contain path traversal sequences or absolute paths, then submits it through the normal analysis workflow.

python

# Security patch in pandora/exceptions.py
# Adds a new exception used as a backstop against path traversal in the extractor

class ZipBomb(PandoraException):
    pass


class PathTransversal(PandoraException):
    pass
# Source: https://github.com/pandora-analysis/pandora/commit/d86ac5b260fb9a41e07f1da1bbd326cdcfc188a7

python

# Security patch in pandora/workers/extractor.py
# Imports the new PathTransversal exception used to reject unsafe extraction paths

from tzlocal import get_localzone_name

from ..default import safe_create_dir, PandoraException
from ..exceptions import ZipBomb, PathTransversal
from ..helpers import Status
from ..pandora import Pandora
from ..report import Report
# Source: https://github.com/pandora-analysis/pandora/commit/d86ac5b260fb9a41e07f1da1bbd326cdcfc188a7

Detection Methods for CVE-2026-88069

Indicators of Compromise

Unexpected files appearing outside the Pandora extraction working directory, particularly under paths owned by the worker process user.
Archive submissions whose entry names contain ../, backslash traversal sequences, or absolute paths such as /etc/ or C:\.
Pandora worker logs showing extraction errors or newly emitted PathTransversal exceptions after patching.
Modification timestamps on Pandora application files or system files that correlate with recent analysis jobs.

Detection Strategies

Enumerate archive entries before extraction and flag any name containing .., leading /, or drive-letter prefixes.
Compare file inventory of the Pandora deployment directory against a known-good baseline to identify unauthorized writes.
Instrument the extractor to log the resolved absolute path of every write and alert when it falls outside the expected extraction root.

Monitoring Recommendations

Enable filesystem auditing (auditd on Linux) on directories the Pandora worker can reach, including configuration and binary locations.
Forward Pandora worker logs to a centralized log platform and alert on PathTransversal exceptions or repeated extraction failures.
Monitor submission telemetry for archives with unusual entry counts, deeply nested paths, or traversal characters.

How to Mitigate CVE-2026-88069

Immediate Actions Required

Update Pandora to a build that includes commit d86ac5b260fb9a41e07f1da1bbd326cdcfc188a7 or later.
Restrict network exposure of Pandora submission endpoints to trusted analysts until the patch is deployed.
Run the Pandora worker as a low-privileged, dedicated system user with write access limited to its extraction directory.
Audit the deployment host for files modified outside the expected extraction directory since the service was first exposed.

Patch Information

The fix resolves each extraction destination path before writing and verifies that it remains below the expected extraction directory. Attempts resolving outside this directory raise a new PathTransversal exception and are rejected. See the GitHub commit update for the full patch.

Workarounds

Disable the archive extraction worker until the patched version is installed if submissions cannot be restricted.
Confine the Pandora worker process using containers, systemd sandboxing, AppArmor, or SELinux to limit reachable write paths.
Mount the extraction directory on a dedicated filesystem or bind mount with nodev, nosuid, and restrictive ownership to reduce blast radius.

bash

# Example systemd hardening for the Pandora worker service
# /etc/systemd/system/pandora-worker.service.d/hardening.conf
[Service]
User=pandora
Group=pandora
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
NoNewPrivileges=true
ReadWritePaths=/var/lib/pandora/extraction
ReadOnlyPaths=/etc/pandora