svglib denial of service via nested SVG use references in svg2rlg
Affects svglib 2.3.0 and earlier in applications that render SVG from an untrusted source. No vendor severity rating is given; CVSS scores it 7.5 (high). Fixed in 2.3.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.3.1
- Who is exposed
- Default setups
Summary
The svglib library from deeplook is affected: a small, attacker-crafted SVG file with nested `<use>` references can make the svg2rlg() renderer expand exponentially, consuming excessive CPU and memory. An attacker can deliver the file remotely, without logging in or any user action, when an application renders it.
Written by a model
Original description
svglib reads SVG files and converts them to other formats. Prior to 2.3.1, the svg2rlg() renderer recursively expands nested SVG <use> references by deep-copying each referenced subtree; SvgRenderer.renderUse() in src/svglib/svglib.py calls xlink_href_target(), which rejects direct cycles but permits acyclic reference graphs with repeated fan-out. A small attacker-controlled SVG can therefore trigger exponentially increasing node expansion, consuming excessive CPU and memory in any application that renders it without a non-default option; HTML-to-PDF workflows using xhtml2pdf can reach the same renderer when an embedded data:image/svg+xml image in an HTML img element is passed to pisa.CreatePDF(). This issue is fixed in 2.3.1.
Who should check
Teams rendering untrusted SVG with svglib 2.3.0 or earlier, including xhtml2pdf HTML-to-PDF pipelines that embed data:image/svg+xml images
“<= 2.3.0 (verified on 2.3.0 and 1.5.1)”
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 2.3.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132275 (svglib: Exponential resource consumption via nested <use> references in svg2rlg), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132275 (entry last updated 2026-11-20):
Affected:
- deeplook svglib: fixed in 2.3.1
Fixed versions: 2.3.1.
Conditions (all must be true for the bug to be hit):
- Applications that render SVG from an untrusted source with svglib (affected versions 2.3.0 and earlier) (source: https://github.com/deeplook/svglib/security/advisories/GHSA-555j-qj3j-c8jv)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-132275 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132275 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/deeplook/svglib/security/advisories/GHSA-555j-qj3j-c8jv
- https://github.com/deeplook/svglib/commit/7380d3c3836940fd75f8e203fff80077b7d5a425
- https://github.com/deeplook/svglib/releases/tag/v2.3.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132275
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132275"}.Affected versions
- deeplook svglibfixed in 2.3.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · deeplook/svglib · Advisory GHSA-555j-qj3j-c8jv |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132275 |
| Record | NVD · CVE-2026-132275 |
| Other links 2 | |
| Repository | GitHub · deeplook/svglib · Commit 7380d3c3 |
| Repository | GitHub · deeplook/svglib · Release v2.3.1 |
Questions about CVE-2026-132275
Is CVE-2026-132275 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Rendering a small crafted SVG that uses nested <use> references makes svglib consume excessive CPU and memory, which can deny service to the application.
Source: github.com
Which versions are affected by CVE-2026-132275?
svglib: before 2.3.1.
Source: cve.now feed data
Am I affected, and how do I check?
Applications that render SVG from an untrusted source with svglib 2.3.0 and earlier are affected. To check, run pip show svglib in the environment where the application runs and compare the version with 2.3.1.
Source: github.com
How do I fix CVE-2026-132275?
Upgrade svglib to version 2.3.1, which is the listed fixed version.
Source: github.com
Related
- CVE-2026-104199aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation
- CVE-2026-127960Denial of service through folded HTTP response headers
- CVE-2026-63202netty-incubator-codec-ohttp BinaryHttpParser: Unauthenticated CPU-exhaustion DoS via infinite loop in field-section decoding
- CVE-2026-63124netty-incubator-codec-ohttp: Binary HTTP parser infinite loop on known-length field section boundary
- CVE-2026-128139NLTK: XMLCorpusView comment and CDATA parsing permits quadratic CPU denial of service
- CVE-2026-129229NLTK: Compile-time regex DoS in NLTK search/tokenizer sinks: quadratic regex-engine compile bypasses the match-only timeout
No corrections so far. Something wrong on this page? Report an error.