Is CVE-2026-41206 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41206 being exploited in the wild.

How severe is CVE-2026-41206?

High severity, with a CVSS score of 7.8, published 23 April 2026.

Which products and versions are affected?

pyspector (PyPI) <= 0.1.7, ECOSYSTEM:introduced=0,fixed=0.1.8.

Is there a fix for CVE-2026-41206?

Yes. pyspector (PyPI): upgrade to 0.1.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2026-41206?

Check whether you run Parzivalhack Pyspector or pyspector (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

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

Q: Which products and versions are affected?

pyspector (PyPI) <= 0.1.7, ECOSYSTEM:introduced=0,fixed=0.1.8.

Q: Is there a fix for CVE-2026-41206?

Yes. pyspector (PyPI): upgrade to 0.1.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: Am I affected by CVE-2026-41206?

Check whether you run Parzivalhack Pyspector or pyspector (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41206 · Severity: high · CVSS 7.8 · Published 2026-04-23

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.

Technologies: pyspector (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-41206 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41206 being exploited in the wild.
How severe is CVE-2026-41206?: High severity, with a CVSS score of 7.8, published 23 April 2026.
Which products and versions are affected?: pyspector (PyPI) <= 0.1.7, ECOSYSTEM:introduced=0,fixed=0.1.8.
Is there a fix for CVE-2026-41206?: Yes. pyspector (PyPI): upgrade to 0.1.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-41206?: Check whether you run Parzivalhack Pyspector or pyspector (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

pyspector (PyPI): upgrade to 0.1.8 or later
```
pip install "pyspector>=0.1.8"
```

Affected products

Parzivalhack Pyspector
pyspector (PyPI) <= 0.1.7, ECOSYSTEM:introduced=0,fixed=0.1.8

Identifiers

CVE-2026-41206
GHSA-vp22-38m5-r39r
PYSEC-2026-3031

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.