CVE-2026-32722 is a low-severity (CVSS 3.6) Cross-site Scripting (XSS) vulnerability in memray. A fix is available for memray — see the affected versions and patch details below.
Memray-generated HTML reports vulnerable to Stored XSS via unescaped command-line metadata
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32722.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
memrayReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Prior to Memray 1.19.2, Memray rendered the command line of the tracked process directly into generated HTML reports without escaping. Because there was no escaping, attacker-controlled command line arguments were inserted as raw HTML into the generated report.
This allowed JavaScript execution when a victim opened the generated report in a browser.
Affected Version
- Memray version:
1.19.1and earlier
Remediation
Upgrade to Memray 1.19.2, and avoid attaching Memray to untrusted processes until you have upgraded.
Root Cause
Jinja is used to embed the process's command line arguments into the generated flame graph or table report. Memray has not been telling Jinja to HTML escape the command line arguments when writing them into the HTML, leading to a stored XSS vulnerability.
Impact
An attacker who can influence the script name or command-line arguments of a profiled program can inject HTML/JavaScript into Memray-generated HTML reports (both memray flamegraph and memray table reports, both with and without --no-web). When a victim opens the generated report in a browser, the injected JavaScript executes in the context of the report.
Note that in the case of memray attach, the user attaching Memray and generating the report may be a different user than the one who ran the command and set up the command line arguments.
Proof of Concept
Run Memray on a script with an attacker-controlled filename:
touch '<img src=x onerror=alert(1)>'
python -m memray run -o poc.bin '<img src=x onerror=alert(1)>'
Generate a report:
python -m memray flamegraph -o poc.html poc.bin
Observed Result
The generated HTML contains raw unescaped attacker-controlled HTML.
Opening or reloading the generated report in a browser triggers JavaScript execution.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | memray | all versions | 1.19.2pip install --upgrade 'memray==1.19.2' |
Affected Products
memraybloombergDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for memray, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update memray to 1.19.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32722 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2026-32722 in your dependencies?
Find it across PyPI, including transitive dependencies.