Skip to main content
VulnerabilityPublished Updated

CVE-2026-33140: ParzivalHack PySpector · Cross-site Scripting

Affects ParzivalHack PySpectorSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.1.7 when convenient.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.1.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade PySpector and pyspector to 0.1.7.

Affected software

ProductAffectedFixed in
ParzivalHackPySpectorAffected
  • <0.1.7
Fixed in
  • 0.1.7
PyPIpyspectorpkg:pypi/pyspectorOther threatsAffected
  • <0.1.7
Fixed in
  • 0.1.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations and users should immediately upgrade PySpector to version 0.1.7 or later, where the issue has been patched. Until upgrading, users should avoid opening HTML reports generated by PySpector versions prior to 0.1.7, especially reports generated from untrusted or potentially malicious Python source files. Implement strict controls on the source files scanned by PySpector to prevent injection of malicious JavaScript payloads. Additionally, consider opening PySpector reports in isolated or sandboxed browser environments to limit potential damage from script execution. Security teams should review their development and testing workflows to ensure that report files are validated and sanitized before distribution. Incorporating automated scanning of generated reports for embedded scripts could also help detect attempts to exploit this vulnerability.

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 stored Cross-Site Scripting (XSS) vulnerability in the HTML report generator. When PySpector scans a Python file containing JavaScript payloads (i.e.inside a string passed to eval() ), the flagged code snippet is interpolated into the HTML report without sanitization. Opening the generated report in a browser causes the embedded JavaScript to execute in the browser's local file context. This issue has been patched in version 0.1.7.

References

Community reviews

Loading reviews…