https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 09:15:12 +0000 https://vulnerability.circl.lu/vuln/cve-2026-33140 <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&#39;s local file context. This issue has been patched in version 0.1.7.</p> <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&#39;s local file context. This issue has been patched in version 0.1.7.</p> https://vulnerability.circl.lu/vuln/cve-2026-33140 https://vulnerability.circl.lu/vuln/ghsa-2gmv-2r3v-jxj2 <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&#39;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&#39;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=&#34;871&#34; height=&#34;752&#34; alt=&#34;image&#34; src=&#34;https://github.com/user-attachments/assets/1b0a57f2-3632-4347-a…</p> <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&#39;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&#39;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=&#34;871&#34; height=&#34;752&#34; alt=&#34;image&#34; src=&#34;https://github.com/user-attachments/assets/1b0a57f2-3632-4347-a…</p> https://vulnerability.circl.lu/vuln/ghsa-2gmv-2r3v-jxj2