CVE-2026-33139: Parzivalhack Pyspector vulnerability (CVSS 7.8)

Description

PySpector is a static analysis security testing (SAST) Framework engineered for modern Python development workflows. PySpector versions 0.1.6 and prior are affected by a security validation bypass in the plugin system. The validate_plugin_code() function in plugin_system.py, performs static AST analysis to block dangerous API calls before a plugin is trusted and executed. However, the internal resolve_name() helper only handles ast.Name and ast.Attribute node types, returning None for all others. When a plugin uses indirect function calls via getattr() (such as getattr(os, 'system')) the outer call's func node is of type ast.Call, causing resolve_name() to return None, and the security check to be silently skipped. The plugin incorrectly passes the trust workflow, and executes arbitrary system commands on the user's machine when loaded. This issue has been patched in version 0.1.7.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityLow

Privileges requiredNone

User interactionRequired

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

Parzivalhack Pyspector< 0.1.7

Remediation

Fixed in

Parzivalhack Pyspector≥ 0.1.7

Patch & vendor advisories

https://github.com/ParzivalHack/PySpector/security/advisories/GHSA-v3xv-8vc3-h2m6

References

https://github.com/ParzivalHack/PySpector/security/advisories/GHSA-v3xv-8vc3-h2m6ExploitVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-33139 being actively exploited?

CVE-2026-33139 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.18%.

How severe is CVE-2026-33139?

CVE-2026-33139 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.18% probability of exploitation.

Which products are affected by CVE-2026-33139?

Affected products include Parzivalhack Pyspector.

How do I fix CVE-2026-33139?

Upgrade affected software to a fixed version, for example Parzivalhack Pyspector 0.1.7 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-33139 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo