Skip to content
Fencer Intel
critical 9.1

CVE-2019-15058 json

stb_image.h (aka the stb image loader) 2.23 has a heap-based buffer over-read in stbi__tga_load, leading to Information Disclosure or Denia…

published 7y ago modified 4mo ago also EUVD-2019-6142

cvss
9.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

stb_image.h (aka the stb image loader) 2.23 has a heap-based buffer over-read in stbi__tga_load, leading to Information Disclosure or Denial of Service.

Patch / fix

  • libstb Debian 14, Debian 13, Debian 12 0.0~git20210910.af1a5bc+ds-1

debian advisories DEBIAN-CVE-2019-15058

Is CVE-2019-15058 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2019-15058 updated cvss 9.1

stbi: heap-based buffer overflow in stbi__tga_load function in stb_image.h

  • Red Hat Enterprise Linux 6 clutter
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 cogl, compat-libcogl12, compat-libcogl-pango12 Red Hat Enterprise Linux 8 cogl, SFML
    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

Exploit prediction

2.80% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/nothings/stb/issues/790 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel 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.