Cross-Site Scripting (XSS) in memray (CVE-2026-32722)
Summary
Cross-site scripting in memray (CVE-2026-32722). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.19.2 or later.
Original description
The description as published by the source.
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 ''
python -m memray…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32722 has been found in memray.
Risk of unauthorized operations or information disclosure.
What to do: upgrade memray to 1.19.2 or later.
If unsure, ask your IT team or search "memray CVE-2026-32722" on the vendor's site.
CVE-2026-32722 (memray) — CWE-79
Attack vector: local / unauthenticated
Patched: 1.19.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in memray.
Check the vendor advisory for the affected versions of memray.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.19.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'memray' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'memray' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
memrayを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade memray to 1.19.2ステージング環境で 1.19.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-32722 python-memray
- Ubuntu UBUNTU-CVE-2026-32722 python-memray
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com