Pandora Has a 9.3 Path Traversal. Your Malware Analyzer Can Write Outside Its Sandbox

• The Mess: Pandora’s archive extraction worker trusts file paths supplied inside malicious archives and can write extracted files outside the intended directory.
• The Damage: An unauthenticated attacker can overwrite files accessible to the Pandora worker and potentially turn a malware-analysis box into a foothold.
• The Fix: Patch Pandora and make sure every extraction destination is canonicalized and verified before anything reaches the filesystem.

Pandora is built to analyze suspicious files.

That makes its file extraction code part of the security boundary.

CVE-2026-88069 breaks that boundary.

The vulnerability is a path traversal in Pandora’s archive extraction worker. A specially crafted archive or disk image can contain attacker-controlled paths that escape the directory where Pandora expects the files to be extracted.

The result is an arbitrary file-write primitive.

Not arbitrary code execution by itself.

But arbitrary file writes are exactly the sort of primitive attackers can turn into something much worse when the vulnerable process has access to application configuration, scripts, credentials or system files.

The Sandbox Wasn’t a Sandbox

The extraction worker is supposed to take something like:

/analysis/sample.zip

and safely unpack it underneath a controlled directory.

The vulnerable logic failed to guarantee that the final destination stayed there.

An archive can contain paths using traversal sequences or other crafted path representations. If the application accepts those paths without resolving and validating the final destination, the attacker can escape the extraction root.

That is the classic CWE-22 path traversal problem.

The particularly ugly part is where this code runs.

Pandora is malware-analysis infrastructure.

If an attacker can submit a malicious archive for analysis, the archive itself becomes the delivery mechanism for the filesystem attack.

No Password Required

The CVSS 4.0 score is 9.3 Critical.

The vector gives the vulnerability:

• network attack vector;
• low attack complexity;
• no attack requirements;
• no privileges required;
• no user interaction required;
• high integrity impact;
• high availability impact.

There is an important qualification.

The attacker needs to be able to submit a malicious archive or disk image to Pandora for analysis.

The flaw is therefore not “send one packet to any Pandora server and instantly get root.”

The actual impact depends on what the Pandora worker can write.

That distinction matters.

So does the potential impact.

Arbitrary File Writes Are Enough to Get Interesting

If the extraction worker can overwrite files used by Pandora itself, an attacker may be able to modify application configuration or other files that influence later execution.

If it can reach sensitive system files, the consequences can become even worse.

The CVE description explicitly warns that exploitation can cause unauthorized modification of application or system files, denial of service and potentially further compromise depending on the worker’s permissions.

That is why calling this merely an “archive extraction bug” undersells it.

The archive is just the delivery vehicle.

The real vulnerability is that attacker-controlled filenames cross a filesystem security boundary.

The Fix Checks the Final Destination

The security fix changes the extraction logic so Pandora resolves the destination path before writing and verifies that the resulting path remains underneath the intended extraction directory.

Anything resolving outside that directory is rejected as a path-traversal attempt.

That is the correct security model.

Do not ask whether the original string looks safe.

Resolve it.

Then verify where it actually points.

Pandora Versions Up to 1.12.7 Are Affected

CVE-2026-88069 affects Pandora versions 1.12.7 and earlier according to the published CVE record.

The published record references the Pandora project’s security fix commit, d86ac5b260fb9a41e07f1da1bbd326cdcfc188a7.

Administrators should:

• identify Pandora installations running 1.12.7 or earlier;
• deploy the project fix;
• restrict who can submit files for analysis;
• inspect extraction logs for rejected or suspicious paths;
• review files modified by Pandora workers;
• run the worker with the minimum filesystem permissions possible;
• isolate the analysis environment from sensitive infrastructure.

And do not assume that putting Pandora inside a “sandbox” solves the problem.

If the sandbox itself contains a path traversal bug, the attacker may simply attack the walls.

No CISA KEV Entry

CVE-2026-88069 is currently not listed in CISA’s Known Exploited Vulnerabilities catalog, and there is no confirmed active exploitation in the sources reviewed for this article.

That does not make the vulnerability harmless.

A remotely reachable, unauthenticated archive-extraction flaw with a 9.3 CVSS score is exactly the sort of bug that deserves attention before somebody turns it into an exploit chain.

Bugstoday Opinion

Security products get a free pass far too often.

They inspect malware, so people assume the inspection environment is automatically hardened.

It isn’t.

A malware analyzer processes hostile files by definition.

Every parser, decompressor, extractor and converter inside it is sitting directly on the front line.

Pandora just demonstrated why.

The attacker doesn’t have to escape a VM with a fancy kernel exploit.

Sometimes all they need is a filename containing ../.

Today’s Bugs. Tomorrow’s Breaches.

Technical Sources

CVE-2026-88069

CIRCL Vulnerability-Lookup

Pandora Analysis — security fix commit

Rapid7 Vulnerability Database

Tenable CVE Database