<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T09:15:12.673473+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-33140</id>
    <title>CVE-2026-33140 — PySpector: Stored XSS in PySpector HTML Report Generation leads to Javascript Code Execution</title>
    <updated>2026-10-02T09:15:12.704503+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> ParzivalHack PySpector</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-33140"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-2gmv-2r3v-jxj2</id>
    <title>GHSA-2gmv-2r3v-jxj2 — Stored XSS in PySpector HTML Report Generation leads to Javascript Code Execution</title>
    <updated>2026-10-02T09:15:12.704788+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: pyspector</p>
<p>### Summary
PySpector versions `&lt;= 0.1.6` 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.</p>
<p>### Impact
An attacker can craft a malicious Python file (for example, hosted in a public repository), designed to be scanned by PySpector. When a victim scans this file and opens the resulting HTML report, arbitrary JavaScript executes in their browser. While the `file://` context limits the attacker's ability to exfiltrate cookies or make credentialed requests, the following is still achievable:
- Arbitrary DOM manipulation
- Redirects to attacker-controlled pages
- Theft of locally accessible data via `fetch()` or `XMLHttpRequest` to `file://` paths (browser-dependent)</p>
<p>Any user of PySpector who scans untrusted code and generates HTML reports, is potentially affected.</p>
<p>### PoC</p>
<p>The following steps reproduce the vulnerability on PySpector `&lt;= 0.1.6`:
1. Create a malicious Python file containing a JavaScript payload embedded in a string argument to `eval()`, and run PySpector against the file, generating an HTML report:
&lt;img width="871" height="752" alt="image" src="https://github.com/user-attachments/assets/1b0a57f2-3632-4347-a…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-2gmv-2r3v-jxj2"/>
  </entry>
</feed>
