How severe is CVE-2026-41206?

CVE-2026-41206 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-41206 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-41206?

CVE-2026-41206 affects Parzivalhack Pyspector. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-41206?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-41206 have an EU (EUVD) identifier?

Yes. CVE-2026-41206 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-25160.

When was CVE-2026-41206 published?

CVE-2026-41206 was published on 2026-04-23 and last updated on 2026-06-17.

CVE-2026-41206

CVE-2026-41206 is a high-severity vulnerability in Parzivalhack Pyspector with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-184.

Key facts

Severity: High (CVSS 3.x base score 7.8)
CVSS v4: 6.9
EPSS exploit prediction: 0% (8th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-25160
Weakness: CWE-184
Affected product: Parzivalhack Pyspector
Published: 2026-04-23
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-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 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.
How severe is CVE-2026-41206?: CVE-2026-41206 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-41206 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-41206?: CVE-2026-41206 affects Parzivalhack Pyspector. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-41206?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-41206 have an EU (EUVD) identifier?: Yes. CVE-2026-41206 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-25160.
When was CVE-2026-41206 published?: CVE-2026-41206 was published on 2026-04-23 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:parzivalhack:pyspector:*:*:*:*:*:python:*:*

More vulnerabilities in Parzivalhack Pyspector

CVE-2026-33139 — High (CVSS 7.8): PySpector is a static analysis security testing (SAST) Framework engineered for modern Python development workflows.…
CVE-2026-33140 — Medium (CVSS 6.1): PySpector is a static analysis security testing (SAST) Framework engineered for modern Python development workflows.…

All CVEs affecting Parzivalhack Pyspector →

Other CWE-184 vulnerabilities

CVE-2026-28363 — Critical (CVSS 9.9): In OpenClaw before 2026.2.23, tools.exec.safeBins validation for sort could be bypassed via GNU long-option…
CVE-2026-56315 — Critical (CVSS 9.8): picklescan before 1.0.4 fails to block at least seven Python standard library modules (including uuid, _osx_support,…
CVE-2026-53873 — Critical (CVSS 9.8): picklescan before 1.0.4 contains an incomplete blocklist for the profile module that fails to block the module-level…
CVE-2025-71323 — Critical (CVSS 9.8): picklescan before 0.0.33 fails to block the ctypes module, allowing attackers to achieve remote code execution by…
CVE-2025-71320 — Critical (CVSS 9.8): picklescan before 0.0.33 contains an incomplete deny-list that fails to block pydoc.locate and operator.methodcaller…
CVE-2026-41264 — Critical (CVSS 9.8): Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, the specific…

Browse all CWE-184 vulnerabilities →