HomeIntelligenceBrief
VULNERABILITY BRIEF🟠 High Vulnerability

Pulpy 0.1.1‑Beta Filesystem Sandbox Bypass (CVE‑2026‑44225) Allows Arbitrary File Access

Pulpy 0.1.1‑Beta’s sandbox uses an incomplete blocklist, letting malicious apps read/write any file in a user’s home directory. The issue highlights a control‑gap that SOC 2 audits require documented remediation for, making continuous control mapping essential.

LiveThreat™ Intelligence · 📅 July 07, 2026· 📰 exploit-db.com
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
Actions
2 recommended
📰
Source
exploit-db.com

Pulpy 0.1.1‑Beta Filesystem Sandbox Bypass (CVE‑2026‑44225)

What Happened – A blocklist‑based path validation routine in Pulpy 0.1.1‑Beta (an open‑source web‑app packaging framework) fails to block user‑home directories such as ~/ .ssh/, ~/ .aws/, and ~/Documents/. An attacker who can inject JavaScript into a Pulpy‑packaged app can read or write arbitrary files in the victim’s home folder, effectively escaping the intended sandbox.

Why It Matters for Compliance & Audit Readiness

  • The flaw illustrates a classic control‑gap: a security control (filesystem sandbox) is present but improperly implemented, leaving a gap that would be flagged in a SOC 2 CC7.1 – System Operations assessment.
  • Continuous evidence of control design, testing, and remediation is required to demonstrate that “the system is protected against unauthorized access to data.” Mapping this vulnerability to the relevant control and capturing remediation evidence satisfies that requirement.
  • Verisq’s Control Mapping capability can automatically link the discovered gap to the appropriate SOC 2 control, collect remediation tickets, and generate audit‑ready evidence for the Trust Center.

Who Is Affected – Any organization that builds, distributes, or runs desktop/web applications packaged with Pulpy 0.1.1‑Beta, across all sectors (e.g., fintech, health‑tech, SaaS, internal tooling).

Recommended Actions

  • Upgrade to a patched version of Pulpy (or apply the vendor’s hot‑fix) that implements full path canonicalization and a deny‑list covering user‑home directories.
  • Conduct a control‑mapping review: map the filesystem sandbox control to SOC 2 CC7.1, capture remediation evidence, and update your continuous‑compliance dashboard.
  • Add automated static‑code analysis or SCA rules to detect similar weak prefix checks in future releases.

Source: Exploit‑DB 52616

Technical Notes – The vulnerability resides in src/bridge/native_modules.mm where a simple find("/Library/") == 0 check is used. It bypasses the sandbox for any path not starting with the hard‑coded root prefixes (/etc/, /var/, /usr/, /System/, /Library/). No CVSS score is published yet; the exploit works on macOS and Linux. Source: Exploit‑DB 52616

📰 Original Source
https://www.exploit-db.com/exploits/52616

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Every gap like this maps to a control you can evidence.

The Verisq AI Trust Operations platform maps incidents to your control framework and collects the evidence continuously — so your Trust Center shows proof, not promises, when a buyer or auditor asks.

Explore the Verisq AI Trust Operations platform →