Vulnerability · CVE-2026-41206
PySpector is a static analysis security testing (SAST) Framework engineered for modern Python development workflows.
Published Apr 23, 2026 · catalog updated Jun 17, 2026 · PySpector is a static
Check if you run it
No confirmed exploitation is on record for CVE-2026-41206. EPSS is 0.19%. Act only if a listed version of PySpector is a static is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (PySpector is a static).
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium6.9
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.19%
- Remediation
- Advisory link
- Affected products
- cpe parzivalhack/pyspector
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 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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe parzivalhack/pyspectorversion unspecified
How to fix CVE-2026-41206
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-41206. EPSS is 0.19%. Act only if a listed version of PySpector is a static is installed.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-184. EPSS 0.19%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Apr 23, 2026 · NIST NVD
Detected
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 is incomplete and can be bypassed using several Python constructs that are not checked. An attacker
Jun 17, 2026 · NIST NVD
Updated
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 is incomplete and can be bypassed using several Python constructs that are not checked. An attacker
Sources
- CVE.orgVulnerability recordCVE-2026-41206
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-41206
30-day exploitation probability 0.2%
first.org - NIST NVDVulnerability recordCVE-2026-41206
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 block
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.