CVE-2026-5185

Received Received - Intake

Heap-Based Buffer Overflow in stb_image Multi-Frame GIF Handler

Publication date: 2026-03-31

Last updated on: 2026-04-29

Assigner: VulDB

Description

A security flaw has been discovered in Nothings stb_image up to 2.30. This affects the function stbi__gif_load_next of the file stb_image.h of the component Multi-frame GIF File Handler. The manipulation results in heap-based buffer overflow. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-03-31

Last Modified

2026-04-29

Generated

2026-07-06

AI Q&A

2026-03-31

EPSS Evaluated

2026-07-05

NVD

CVE-2026-5185

EUVD

EUVD-2026-17337

Affected Vendors & Products

Vendor	Product	Version / Range
nothing	sbt_image	to 2.30 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-122	A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
CWE-119	The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

Attack-Flow Graph

Executive Summary

This vulnerability is a security flaw found in the stb_image library, specifically in the function stbi__gif_load_next within the Multi-frame GIF File Handler component. It causes a heap-based buffer overflow, which means that the program writes more data to a buffer located in the heap than it can hold, potentially leading to memory corruption.

The flaw affects versions of stb_image up to 2.30 and requires local access to exploit. The exploit code has been publicly released, making it easier for attackers to use this vulnerability.

Impact Analysis

This vulnerability can lead to a heap-based buffer overflow, which may allow an attacker with local access to corrupt memory. This could result in unexpected behavior such as application crashes or potentially allow the attacker to execute arbitrary code with the privileges of the affected application.

Since the exploit is publicly available, the risk of exploitation is higher, especially in environments where local access is possible.

Hi! I’m here to help you understand CVE-2026-5185. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70