Vulnerabilities in pkg:pypi/pyspector
PACKAGECVE-2026-41206 is a MODERATE pyspector has a plugin code vulnerability (CWE-184: Incomplete List of Disallowed Inputs) affecting Pyspector libraries in the PyPI ecosystem. The issue involves pyspector has a plugin code execution bypass via incomplete static analysis in pluginsecurity.validate_plugin_code. Remediation is available by upgrading affected packages to version 0.1.8.
pkg:pypi/pyspector
Vulnerability advisories affecting package pkg:pypi/pyspector. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-vp22-38m5-r39r | CVE-2026-41206 | MODERATE | PySpector has a Plugin Code Execution Bypass via Incomplete Static Analysis in PluginSecurity.validate_plugin_code |
| GHSA-2gmv-2r3v-jxj2 | CVE-2026-33140 | MODERATE | Stored XSS in PySpector HTML Report Generation leads to Javascript Code Execution |
| GHSA-v3xv-8vc3-h2m6 | CVE-2026-33139 | HIGH | PySpector has a Plugin Sandbox Bypass leads to Arbitrary Code Execution |
CVE-2026-41206 at a Glance
How to Fix CVE-2026-41206
To remediate this vulnerability, upgrade all affected Pyspector dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install pyspector>=0.1.8
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show pyspector
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-41206, inspect your installed packages using pip:
pip show pyspector
Analyze the terminal output to locate any version of Pyspector in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.1.8), your application is affected.
Note: The pip show pyspector command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-184: Incomplete List of Disallowed Inputs, where 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. In Pyspector, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-41206 Affected Pyspector Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
pyspector
|
PyPI |
< 0.1.8
|
0.1.8
|
References
Frequently Asked Questions
What is CVE-2026-41206?
Which Pyspector versions are affected?
What version fixes CVE-2026-41206?
Is pyspector affected?
What CWE is associated with CVE-2026-41206?
How can I check PyPI dependencies for CVE-2026-41206?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-vp22-38m5-r39r",
"modified" : "2026-04-24T20:53:36Z",
"published" : "2026-04-16T01:09:17Z",
"aliases" : [ "CVE-2026-41206" ],
"summary" : "PySpector has a Plugin Code Execution Bypass via Incomplete Static Analysis in PluginSecurity.validate_plugin_code",
"details" : "### Summary\n\nThe plugin security validator in PySpector uses AST-based static analysis to prevent dangerous code from being loaded as plugins. 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.\n\n### Details\n\nThe validator maintains a set called `fatal_calls` that enumerates explicitly forbidden function names and attribute access patterns such as eval, exec, `os.system`, and `subprocess.Popen`. However, this approach relies on an exhaustive blocklist of known-dangerous identifiers, which is inherently incomplete.\n\nThe following bypass techniques are not detected by the current implementation:\n\n`importlib.import_module` is not in `fatal_calls` and is not treated as a dangerous module, so it can be used to load os, subprocess, or any other module at runtime without triggering the validator.\n\nDynamic attribute chains using `__class__.__mro__` and related dunder attributes allow traversal of the class hierarchy to reach arbitrary built-in functions without naming them directly in the source.\n\nctypes is not blocked and can be used to call native library functions including system.\n\n`__builtins__` dictionary access exposes all built-in callables without using the names that the validator checks.\n\n`types.CodeType` allows construction and execution of raw code objects.\n\nThe alias resolution in the AST visitor only handles simple import X as Y cases, so aliased imports of blocked modules evade detection, and transitive imports through unblocked modules are never examined.\n\nBecause the validator produces a pass/fail result that gates plugin installation with the --trust flag, a bypass causes untrusted plugin code to execute with the full privileges of the PySpector process.\n\n### PoC\n\n```python\nimport textwrap, tempfile, os\n\nevil_plugin = textwrap.dedent(\"\"\"\nimport importlib\nmod = importlib.import_module('os')\nmod.system('id > /tmp/pwned')\n\"\"\")\n\nwith tempfile.NamedTemporaryFile(suffix=\".py\", mode=\"w\", delete=False) as f:\n f.write(evil_plugin)\n plugin_path = f.name\n\nfrom pyspector.plugin_system import PluginSecurity\n\nresult = PluginSecurity.validate_plugin_code(plugin_path)\nprint(\"Validation passed:\", result)\n\nexec(compile(open(plugin_path).read(), plugin_path, \"exec\"))\n\nprint(\"Command output:\", open(\"/tmp/pwned\").read())\nos.unlink(plugin_path)\n```\n\n### Impact\n\nAny user or process that can supply a plugin file to PySpector and invoke the plugin installation workflow can execute arbitrary operating system commands with the privileges of the PySpector process. The static analysis check provides a false sense of security, as it can be circumvented trivially using standard library modules that are present in every Python installation. All versions of PySpector that include the plugin system are affected.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "pyspector"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.1.8"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.1.7"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/ParzivalHack/PySpector/security/advisories/GHSA-vp22-38m5-r39r"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-41206"
}, {
"type" : "WEB",
"url" : "https://github.com/ParzivalHack/PySpector/commit/3c9547157fc07396f22b26b3484a9a91eba98555"
}, {
"type" : "WEB",
"url" : "https://github.com/ParzivalHack/PySpector/commit/4e279e078c53d760fd321ff9b698d683c65ccb8e"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/ParzivalHack/PySpector"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-184" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-16T01:09:17Z",
"nvd_published_at" : "2026-04-23T02:16:18Z"
}
}