CVE-2024-55456 json
lunasvg v3.0.1 was discovered to contain a segmentation violation via the component gray_find_cell
published 2025-02-03 21 mo ago modified 2026-06-17 4 mo ago also PYSEC-2025-127 , EUVD-2024-52773
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
lunasvg v3.0.1 was discovered to contain a segmentation violation via the component gray_find_cell
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-55456 updated cvss 8.1
lunasvg: From CVEorg collector
-
Red Hat All currently supported Red Hat productsnot 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
- no
- Technical impact
- partial
- Assessed
- 21 mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/sammycage/lunasvg/issues/199 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | lunasvg | <=3.0.1 |
no fix listed |
Classification
- Weakness
-
- CWE-653 Improper Isolation or Compartmentalization
References
-
github.com
/sammycage/lunasvg/issues/199
exploit, issue-tracking, vendor-advisory, report
Sources
- CVE List CVE-2024-55456
- NVD CVE-2024-55456
- OSV PYSEC-2025-127
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.