Network isolation bypass via proxy-only enforcement
Published Sep 15, 2026 · Updated Sep 15, 2026
Protection mechanism failure in PraisonAI 1.2.3 through 1.7.1 allows remote authenticated users to bypass isolation via direct sockets. SandboxExecutor.buildEnv() sets invalid proxy environment variables but establishes no namespace, firewall, socket filter, or other operating-system boundary. Exploitation requires control of a command executed in network-isolated mode and grants access to services and data reachable from the host.
Summary
What happened
Protection mechanism failure in PraisonAI 1.2.3 through 1.7.1 allows remote authenticated users to bypass isolation via direct sockets. SandboxExecutor.buildEnv() sets invalid proxy environment variables but establishes no namespace, firewall, socket filter, or other operating-system boundary. Exploitation requires control of a command executed in network-isolated mode and grants access to services and data reachable from the host.
The record
- CVE
- CVE-2026-57135
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- PraisonAI
- Product
- PraisonAI
- Classifications
- CWE-653, CWE-693, T1041
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.2.3, < 1.7.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Local loopback SandboxExecutor proof of vulnerabilityproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo