lunasvg v3.0.0 was discovered to contain a allocation-size-too-big bug via the component plutovg_surface_create.

published 2025-01-23 21 mo ago modified 2026-06-17 4 mo ago also PYSEC-2025-131 , EUVD-2024-53720

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits: 0; none known

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-57722 updated 2025-11-21 cvss 6.5

lunasvg: Allocation-size-too-big violation in lunasvg

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: partial
Assessed: 21 mo ago (2025-01-23)

Exploit prediction

0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/keepinggg/poc/blob/main/poc_of_lunasvg_3.1.0 referenced PoC, tagged "exploit" by a source, unverified
github.com https://github.com/sammycage/lunasvg/issues/209 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
pypi	lunasvg	<=3.0.0 <=3.1.0	no fix listed

Classification

Weakness

CWE-770 Allocation of Resources Without Limits or Throttling

References

github.com /keepinggg/poc/blob/main/poc_of_lunasvg_3.1.0
exploit, third-party-advisory, evidence
github.com /sammycage/lunasvg/issues/209
exploit, issue-tracking, vendor-advisory, report

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary