svg-sanitizer from 0.5.0 before 1.1.0 contains an incomplete filtering vulnerability that allows attackers to bypass
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.1.0 when convenient.
Data as of 3 Nov 2026, 16:15 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 5.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 4.3 |
- Patch
- Available – fixed in 1.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade svg-sanitizer to 1.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| darylldoylesvg-sanitizer | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, users should avoid processing untrusted SVG files with vulnerable versions of svg-sanitizer or implement additional filtering to block CSS escape sequences in url() functions.
Description
svg-sanitizer versions from 0.5.0 up to but not including 1.1.0 have a vulnerability where attackers can bypass remote URL removal by using CSS escape sequences inside url() in SVG presentation attributes. This allows crafted SVG files with attributes like fill containing escaped slashes to cause browsers to resolve remote URLs, triggering external requests and potentially enabling data exfiltration.