CVE-2019-1010258 json
nanosvg library nanosvg after commit c1f6e209c16b18b46aa9f45d7e619acf42c29726 is affected by: Buffer Overflow.
published 2019-05-15 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-2000
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
nanosvg library nanosvg after commit c1f6e209c16b18b46aa9f45d7e619acf42c29726 is affected by: Buffer Overflow. The impact is: Memory corruption leading to at least DoS. More severe impact vectors need more investigation. The component is: it's part of a svg processing library. function nsvg__parseColorRGB in src/nanosvg.h / line 1227. The attack vector is: It depends library usage. If input is passed from the network, then network connectivity is enough. Most likely an attack will require opening a specially crafted .svg file.
Exploit prediction
1.77% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/memononen/nanosvg/issues/136 referenced PoC, tagged "exploit" by a source, unverified
- 0day.work https://0day.work/cve-2019-1000032-memory-corruption-in-nanosvg/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Affected products
- nanosvg library nanosvg
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/memononen/nanosvg/issues/136
exploit, third-party-advisory
-
0day.work
/cve-2019-1000032-memory-corruption-in-nanosvg/
exploit, third-party-advisory
-
github.com
/memononen/nanosvg/
third-party-advisory
Sources
- CVE List CVE-2019-1010258
- NVD CVE-2019-1010258
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.