ParzivalHack PySpector up to 0.1.7 PluginSecurity.validate_plugin_code incomplete blacklist

Summaryinfo

A vulnerability has been found in ParzivalHack PySpector up to 0.1.7 and classified as critical. Impacted is the function PluginSecurity.validate_plugin_code. This manipulation causes incomplete blacklist. The identification of this vulnerability is CVE-2026-41206. The attack can only be executed locally. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in ParzivalHack PySpector up to 0.1.7. It has been declared as critical. Affected by this vulnerability is the function PluginSecurity.validate_plugin_code. The manipulation with an unknown input leads to a incomplete blacklist vulnerability. The CWE definition for the vulnerability is CWE-184. The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete, leading to resultant weaknesses. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

PySpector is a static analysis security testing (SAST) Framework engineered for modern Python development workflows. The plugin security validator in PySpector uses AST-based static analysis to prevent dangerous code from being loaded as plugins. Prior to version 0.1.8, the blocklist implemented in `PluginSecurity.validate_plugin_code` is incomplete and can be bypassed using several Python constructs that are not checked. An attacker who can supply a plugin file can achieve arbitrary code execution within the PySpector process when that plugin is installed and executed. Version 0.1.8 fixes the issue.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-41206 since 04/18/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1562.006 for this issue.

Upgrading to version 0.1.8 eliminates this vulnerability. Applying the patch 3c9547157fc07396f22b26b3484a9a91eba98555 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-25160). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• ParzivalHack

Name

• PySpector

Version

• 0.1.0
• 0.1.1
• 0.1.2
• 0.1.3
• 0.1.4
• 0.1.5
• 0.1.6
• 0.1.7

License

• open-source

Website

• Product: https://github.com/ParzivalHack/PySpector/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion