Skip to main content
VulnerabilityPublished

CVE-2026-121445: darylldoyle svg-sanitizer · Unchecked Error Condition

Affects darylldoyle svg-sanitizerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 1.1.0 soon.

Data as of 3 Nov 2026, 14:58 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.2
CNA (VulnCheck)CVSS 3.15.9
Patch
Available – fixed in 1.1.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 darylldoyle svg-sanitizer to 1.1.0.

Affected software

ProductAffectedFixed in
darylldoylesvg-sanitizerAffected
  • >=1.0.0 <1.1.0
Fixed in
  • 1.1.0

AI-suggested

Upgrade to svg-sanitizer version 1.1.0 or later, where this vulnerability is fixed. No other mitigations are specified. Users should ensure the removeRemoteReferences option is used with patched versions to avoid this issue.

Description

CVE-2026-121445 is a high-severity vulnerability in darylldoyle's svg-sanitizer versions from 1.0.0 up to but not including 1.1.0. It involves a regular expression denial of service (ReDoS) in the image-set pattern of the stripRemoteCssTokens() function when the removeRemoteReferences option is enabled. Attackers can exploit this by submitting specially crafted SVG files containing many unclosed image-set tokens, which can exhaust CPU resources or trigger PCRE limits, causing the sanitize() function to throw a TypeError and potentially leave unsafe content unsanitized. The issue is fixed in version 1.1.0.

References

Community reviews

Loading reviews…