CVE-2026-32722

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. Limited direct impact.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-03-18 22:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 10:36 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 3.6 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-03-18 22:16 UTC

Last modified

2026-06-17 10:36 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-79 · Cross-site scripting

Record status

Analyzed

Affected

• Bloomberg Memray < 1.19.2

Attack profile CVSS 3.1 · 3.6

Attack vector

Local

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-32722.md and follow it. Check whether this project is affected by CVE-2026-32722. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge