Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Parzivalhack | Pyspector | < 0.1.7 |
Related Weaknesses (CWE)
References
- https://github.com/ParzivalHack/PySpector/security/advisories/GHSA-v3xv-8vc3-h2mExploitVendor Advisory
FAQ
What is CVE-2026-33139?
CVE-2026-33139 is a vulnerability with a CVSS score of 7.8 (HIGH). 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 ...
How severe is CVE-2026-33139?
CVE-2026-33139 has been rated HIGH with a CVSS base score of 7.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-33139?
Check the references section above for vendor advisories and patch information. Affected products include: Parzivalhack Pyspector.