Threat Intelligence Database

PySpector versions prior to 0.1.8 contain an incomplete blocklist in the PluginSecurity.validate_plugin_code function, allowing bypass of input restrictions via unfiltered Python constructs. This can enable an attacker who supplies a malicious plugin file to execute arbitrary code within the PySpector process. The issue is fixed in version 0.1.8.

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 stored Cross-Site Scripting (XSS) vulnerability in the HTML report generator. When PySpector scans a Python file containing JavaScript payloads (i.e.inside a string passed to eval() ), the flagged code snippet is interpolated into the HTML report without sanitization. Opening the generated report in a browser causes the embedded JavaScript to execute in the browser's local file context. This issue has been patched in version 0.1.7.

MediumVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2026-33140#cwe-79

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.

HighVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2026-33139#cwe-184