Application crash via out-of-bounds GIF frame read
Published Apr 1, 2026 · Updated Apr 1, 2026
Out-of-bounds read in stb_image GIF decoding through 2.30 allows attackers to crash applications via a crafted multi-frame GIF. stbi__load_gif_main calculates two_back by subtracting two frame strides from the output base, and stbi__gif_load_next copies through that invalid pointer when disposal method 3 restores a prior frame. An application must pass an untrusted animated GIF to the GIF animation API; successful exploitation terminates the hosting process without reported data modification.
Summary
What happened
Out-of-bounds read in stb_image GIF decoding through 2.30 allows attackers to crash applications via a crafted multi-frame GIF. stbi__load_gif_main calculates two_back by subtracting two frame strides from the output base, and stbi__gif_load_next copies through that invalid pointer when disposal method 3 restores a prior frame. An application must pass an untrusted animated GIF to the GIF animation API; successful exploitation terminates the hosting process without reported data modification.
The record
- CVE
- CVE-2026-5313
- Published
- Apr 1, 2026
- Updated
- Apr 1, 2026
- Vendor
- Sean Barrett
- Product
- stb
- Classifications
- CWE-404, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2026CVE publishedPublication date reported by the CVE source.
- Apr 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0
- Affected versionversion=2.1
- Affected versionversion=2.10
- Affected versionversion=2.11
- Affected versionversion=2.12
- Affected versionversion=2.13
- Affected versionversion=2.14
- Affected versionversion=2.15
- Affected versionversion=2.16
- Affected versionversion=2.17
- Affected versionversion=2.18
- Affected versionversion=2.19
- Affected versionversion=2.2
- Affected versionversion=2.20
- Affected versionversion=2.21
- Affected versionversion=2.22
- Affected versionversion=2.23
- Affected versionversion=2.24
- Affected versionversion=2.25
- Affected versionversion=2.26
- Affected versionversion=2.27
- Affected versionversion=2.28
- Affected versionversion=2.29
- Affected versionversion=2.3
- Affected versionversion=2.30
- Affected versionversion=2.4
- Affected versionversion=2.5
- Affected versionversion=2.6
- Affected versionversion=2.7
- Affected versionversion=2.8
- Affected versionversion=2.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted multi-frame GIF reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo