# CVE-2026-41206: PySpector has a Plugin Code Execution Bypass via Incomplete Static Analysis in PluginSecurity.validate_plugin_code

> An attacker can achieve arbitrary code execution in PySpector by supplying a malicious plugin that bypasses incomplete static analysis checks.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Apr 2026
- **Updated:** 23 Apr 2026
- **Also known as:** GHSA-vp22-38m5-r39r, PYSEC-2026-3031

## What is CVE-2026-41206?

CVE-2026-41206 is a medium-severity code injection vulnerability in ParzivalHack PySpector, published on 23 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2026-41206?

3 open source packages ship an affected version, including pyspector. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyspector` | PyPI | All versions | 0.1.8 |
| `pyspector` | PyPI | All versions | 0.1.8 |
| `pyspector` | PyPI | All versions | 0.1.8 |

Products: Parzivalhack Pyspector.

## How do I fix CVE-2026-41206?

Upgrade pyspector to 0.1.8 or later.

## Is CVE-2026-41206 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41206 exists.

## Other vulnerabilities in ParzivalHack PySpector

- [CVE-2026-33139](https://insights.sbomify.com/CVE-2026-33139/): PySpector: Plugin Sandbox Bypass leads to Arbitrary Code Execution (high 8.3)
- [CVE-2026-33140](https://insights.sbomify.com/CVE-2026-33140/): PySpector: Stored XSS in PySpector HTML Report Generation leads to Javascript Code Execution (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41206 and fix it if it is affected.

What it is: CVE-2026-41206 is a medium-severity code injection vulnerability in ParzivalHack PySpector, published on 23 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41206 exists.

Affected packages and fixed versions:
- pyspector (PyPI): affected all versions; fixed in 0.1.8
- pyspector (PyPI): affected all versions; fixed in 0.1.8
- pyspector (PyPI): affected all versions; fixed in 0.1.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41206/ (Markdown: https://insights.sbomify.com/CVE-2026-41206/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41206
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41206
- OSV: https://osv.dev/vulnerability/CVE-2026-41206

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41206/
Summaries are generated and may contain mistakes; the official description above is the record.