CVE-2026-30141
Deferred Deferred - Pending Action

Buffer Overflow in bitbank2 AnimatedGIF

Vulnerability report for CVE-2026-30141, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-09

Last updated on: 2026-06-09

Assigner: MITRE

Description

An issue was discovered in bitbank2 AnimatedGIF v2.2.0. A buffer overflow in the DecodeLZW function allows remote attackers to cause a denial of service (crash) or potentially execute arbitrary code via a crafted GIF file.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-09
Last Modified
2026-06-09
Generated
2026-06-30
AI Q&A
2026-06-09
EPSS Evaluated
2026-06-28
NVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
bitbank2 animatedgif 2.2.0
bitbank2 animatedgif to 2.2.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.
CWE-120 The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-30141 is a critical buffer overflow vulnerability found in the AnimatedGIF library, specifically in the DecodeLZW function responsible for decompressing GIF images.

The flaw occurs due to insufficient bounds checking during LZW decompression, which leads to heap-based buffer overflows when processing malformed LZW codes that exceed the expected maximum size.

Additionally, improper validation of certain internal indices further worsens heap corruption.

Attackers can exploit this vulnerability by crafting malicious GIF files that trigger the overflow, causing the application to crash or potentially allowing arbitrary code execution.

Impact Analysis

This vulnerability can impact you by allowing remote attackers to cause denial-of-service (DoS) conditions, crashing applications that use the vulnerable AnimatedGIF library when processing malicious GIF files.

More severely, it may allow attackers to execute arbitrary code on the affected system, potentially leading to full system compromise depending on the context in which the library is used.

Detection Guidance

This vulnerability can be detected by analyzing the behavior of the AnimatedGIF library when processing GIF files, especially by using fuzz testing or AddressSanitizer (ASan) to identify heap-buffer-overflow errors during LZW decompression.

A practical approach is to test the system or application with specially crafted GIF files that trigger the buffer overflow, observing for crashes such as SIGSEGV or SIGBUS signals.

While no specific commands are provided, using tools like AddressSanitizer with the application or running fuzz testing frameworks against the GIF decoding functionality can help detect the vulnerability.

Mitigation Strategies

Immediate mitigation steps include implementing strict bounds checking in the DecodeLZW function to ensure that LZW codes do not exceed the expected maximum (typically 4096 for 12-bit LZW).

Additionally, validate GIF file dimensions and compressed data sizes before processing to prevent buffer overflows.

Input sanitization should be added to reject malformed or malicious GIF files that could trigger the vulnerability.

Until a patched version of the library is available, avoid processing untrusted or suspicious GIF files with the affected AnimatedGIF library.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-30141. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart