What’s Vulnerable › Vulnerabilities
CVE-2026-33139: PySpector: Plugin Sandbox Bypass leads to Arbitrary Code Execution
- Severity: high (CVSS 7.8 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: yes
- Published: 2026-03-20 · updated 2026-06-17
- Weakness: CWE-184
Description
PySpector is a static analysis security testing (SAST) Framework engineered for modern Python development workflows. PySpector versions 0.1.6 and prior are affected by a security validation bypass in the plugin system. The validate_plugin_code() function in plugin_system.py, performs static AST analysis to block dangerous API calls before a plugin is trusted and executed. However, the internal resolve_name() helper only handles ast.Name and ast.Attribute node types, returning None for all others. When a plugin uses indirect function calls via getattr() (such as getattr(os, 'system')) the outer call's func node is of type ast.Call, causing resolve_name() to return None, and the security check to be silently skipped. The plugin incorrectly passes the trust workflow, and executes arbitrary system commands on the user's machine when loaded. This issue has been patched in version 0.1.7.
Affected products
- ParzivalHack PySpector: before 0.1.7 — fixed in 0.1.7
How to fix
Upgrade to a fixed version: ParzivalHack PySpector 0.1.7. Check the vendor advisory for mitigations.
References
Get alerted when CVE-2026-33139 or the next vulnerability affects your stack