Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
CairoSVG versions before 2.9.1 take far too long to render an SVG containing a single path element with a very large number of segments in its path data. An attacker who can supply an SVG to be rendered, such as through a service that renders user-uploaded images, can cause a denial of service through high CPU use. Upgrade cairosvg to version 2.9.1 or later. The source gives no workaround.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.7 | High | 4.0 | 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 | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0038, the 32nd percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:08 UTC First seen by agentprime
- 31 Oct 2026, 14:08 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-c3jg-qh8m-j3h2
- OSV: GHSA-c3jg-qh8m-j3h2
- github.com/Kozea/CairoSVG/security/advisories/GHSA-c3jg-qh8m-j3h2
- nvd.nist.gov/vuln/detail/CVE-2026-107378
- github.com/Kozea/CairoSVG/commit/9d63f049f9988d0ddda3eb94564ac3a50a286523
- github.com/Kozea/CairoSVG/commit/a4d585eb374724b79676e9cceaa9e9a1a4358565
- github.com/Kozea/CairoSVG
- github.com/Kozea/CairoSVG/releases/tag/2.9.1