# CVE-2026-107378: CairoSVG: Quadratic-time DoS parsing a crafted SVG > An attacker can cause denial of service by providing a crafted SVG file that triggers quadratic CPU consumption during rendering. - **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 8 Oct 2026 - **Updated:** 8 Oct 2026 - **Also known as:** DEBIAN-CVE-2026-107378, GHSA-c3jg-qh8m-j3h2, PYSEC-2026-4204, ROOT-APP-PYPI-CVE-2026-107378, UBUNTU-CVE-2026-107378, openSUSE-SU-2026:12111-1 ## What is CVE-2026-107378? CVE-2026-107378 is a high-severity denial of service vulnerability in Kozea CairoSVG, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description CairoSVG is an SVG converter based on Cairo, a 2D graphics library. Prior to 2.9.1, rendering an attacker-controlled SVG with a path containing many segments can cause quadratic CPU consumption in cairosvg/path.py. The path tokenizer repeatedly slices and rescans the remaining path data, while draw_markers drains node.vertices with node.vertices.pop(0), causing repeated linear-time work. The svg2png, svg2pdf, and svg2ps APIs reach these operations during ordinary rendering, allowing a sub-megabyte SVG to consume substantial CPU and deny service to a rendering application. This issue is fixed in version 2.9.1. Weakness: CWE-407 (Inefficient Algorithmic Complexity) ## Which versions are affected by CVE-2026-107378? 3 open source packages ship an affected version, including cairosvg. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `cairosvg` | PyPI | All versions | 2.9.1 | | `cairosvg` | PyPI | All versions | 2.9.1 | | `cairosvg` | PyPI | All versions | 2.9.1 | | `python-CairoSVG` | openSUSE:Tumbleweed | All versions | 2.9.1-1.1 | ## How do I fix CVE-2026-107378? Upgrade cairosvg to 2.9.1 or later. ## Is CVE-2026-107378 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107378 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-107378 and fix it if it is affected. What it is: CVE-2026-107378 is a high-severity denial of service vulnerability in Kozea CairoSVG, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107378 exists. Affected packages and fixed versions: - cairosvg (PyPI): affected all versions; fixed in 2.9.1 - cairosvg (PyPI): affected all versions; fixed in 2.9.1 - cairosvg (PyPI): affected all versions; fixed in 2.9.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-107378/ (Markdown: https://insights.sbomify.com/CVE-2026-107378/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107378 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107378 - OSV: https://osv.dev/vulnerability/CVE-2026-107378 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-107378/ Summaries are generated and may contain mistakes; the official description above is the record.