PySpector’s plugin security validator, which relies on AST‑based static analysis to reject unsafe code, contains an incomplete blocklist in PluginSecurity.validate_plugin_code. This flaw allows attackers to embed dangerous Python constructs that bypass the filter, leading to arbitrary code execution inside the PySpector process when an attacker‑supplied plugin is installed and run. The weakness is a form of CWE‑184, where improper flow control permits the execution of unsafe code.

The affected product is ParzivalHack:PySpector, a static‑analysis framework for Python. All releases prior to 0.1.8 are vulnerable; the issue was remedied in version 0.1.8, so any installation of an older version is at risk.

With a CVSS score of 6.9, the vulnerability represents a moderate risk, while the EPSS score of less than 1% indicates that exploitation is unlikely to occur in the immediate future. The vulnerability is not listed in CISA’s KEV catalog. Adversaries would need the ability to supply a plugin file that PySpector installs and executes, so the attack vector is most likely local or within a development environment where plugins are added.