CVE-2026-32722

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Memray is a memory profiler for Python. 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. Version 1.19.2 fixes the issue.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity61% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

March 18, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Stored XSS in Memray-generated HTML reports via unescaped command-line metadata · Advisory · bloomberg/memray · GitHub

https://github.com/bloomberg/memray/security/advisories/GHSA-r5pr-887v-m2w9
github_release Patch Available

v1.19.2

Patch available: bloomberg/memray v1.19.2

https://github.com/bloomberg/memray/releases/tag/v1.19.2
github_commit Patch Available

commit ba6e4e2e9930 (bloomberg/memray)

Patch available: bloomberg/memray v1.19.2 (contains commit ba6e4e2e9930)

https://github.com/bloomberg/memray/commit/ba6e4e2e9930f9641bed7adfdf43c8e2545ce249

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-memray1.17.0+dfsg-11.17.0+dfsg-1+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-memray1.17.0+dfsg-11.19.3+dfsg-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
memray1.0.0 ... 1.9.1 (33 versions)1.19.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 18:08 UTCOSV refresh
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 37 more
  1. 2026-08-24 14:17 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 11:14 UTCEG score recompute
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 07:22 UTCEG score recompute
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 22:09 UTCEG score recompute
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 04:34 UTCEG score recompute
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 05:09 UTCEG score recompute
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 06:57 UTCEG score recompute
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-07 17:29 UTCEG score recompute
  24. 2026-08-06 13:46 UTCEPSS rescore
  25. 2026-08-06 01:37 UTCEG score recompute
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-04 15:10 UTCEPSS rescore
  28. 2026-08-04 10:38 UTCEPSS rescore
  29. 2026-08-04 00:47 UTCEG score recompute
  30. 2026-08-03 10:36 UTCEPSS rescore
  31. 2026-08-02 16:39 UTCEG score recompute
  32. 2026-08-02 02:27 UTCEPSS rescore
  33. 2026-08-01 04:16 UTCEPSS rescore
  34. 2026-07-30 16:28 UTCEPSS rescore
  35. 2026-07-30 01:30 UTCEPSS rescore
  36. 2026-07-27 14:40 UTCEG score recompute
  37. 2026-07-27 14:27 UTCOSV refresh

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-32722?
CVE-2026-32722 is a medium vulnerability published on March 18, 2026. Memray is a memory profiler for Python. 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…
When was CVE-2026-32722 disclosed?
CVE-2026-32722 was first published in the National Vulnerability Database on March 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32722 actively exploited?
CVE-2026-32722 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.8% of all scored CVEs.
What is the CVSS score of CVE-2026-32722?
CVE-2026-32722 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-32722?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32722, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32722

Explore →

Is Your Infrastructure Affected by CVE-2026-32722?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs