Quick answers
- Is CVE-2026-79515 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-79515 being exploited in the wild.
- How severe is CVE-2026-79515?
- Medium severity, with a CVSS score of 4.3, published 9 September 2026.
- Which products and versions are affected?
- Nothings Stb commit 31c1ad3 and prior.
- Is there a fix for CVE-2026-79515?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-79515 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-79515?
- Check whether you run Nothings Stb at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an out-of-bounds read (heap buffer over-read) in the stbtt__GetGlyphShapeTT function at stb_truetype.h line 1780. The root cause occurs when a contour's final vertex is an off-curve point: the code attempts to read vertices[off+n].type, which accesses one byte past the allocated n-element vertex array. The vulnerable code path is triggered via stbtt_GetGlyphShape when parsing a TrueType glyph containing a single contour with only an off-curve point. No authentication is required; an attacker simply provides a crafted TTF file. The impact is a crash due to memory access violation, resulting in denial of service. A patch has been identified in the upstream GitHub repository (nothings/stb issue #1962).
Affected products
- nothings stb commit 31c1ad3 and prior
Timeline
- 2026-06-06: disclosed: Issue reported on GitHub
- 2026-09-09: advisory: CVE-2026-79515 published on NVD