CVE-2026-73650
SVGO removeScripts can leave executable SVG scripts, enabling XSS.
Is CVE-2026-73650 being exploited?
Not confirmed. CVE-2026-73650 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-73650?
CVE-2026-73650 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73650?
Yes. A fix has been recorded for CVE-2026-73650. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73650 affect?
CVE-2026-73650 affects SVGO versions prior to 2.8.3, 3.3.4, 4.0.2 with removeScripts/removeScriptElement enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73650?
Upgrade SVGO to 2.8.3, 3.3.4, or 4.0.2+; re-sanitize/re-optimize SVG assets
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored/served SVGs may contain executable <svg:script> or JS URIs; attackers can run scripts in users' browsers and steal cookies/localStorage.
Immediate action required
- affected>= 1.0.0 and < 2.8.3
- affected>= 3.0.0 and < 3.3.4
- affected>= 4.0.0 and < 4.0.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.