CVE-2026-123616
Received Received - Intake

Unbounded Memory Allocation in imgproxy ICO Loader

Publication date: 2026-11-08

Last updated on: 2026-11-08

Assigner: VulnCheck

Description
imgproxy from 3.3.0 before 4.0.16 contains an unbounded memory allocation vulnerability in the ICO loader that fails to validate the data_size field. Attackers can supply a crafted 23-byte ICO file declaring a ~4GB data_size to trigger memory exhaustion and worker crashes without authentication.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-08
Last Modified
2026-11-08
Generated
2026-11-08
AI Q&A
2026-11-08
EPSS Evaluated
N/A
NVD
CVE-2026-123616
EUVD
EUVD-2026-119375

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
imgproxy imgproxy From 3.3.0 (inc) to 4.0.16 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-789 The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

imgproxy versions 3.3.0 to 4.0.15 have an unbounded memory allocation flaw in the ICO file loader. The vulnerability occurs because the data_size field in ICO files is not properly validated. Attackers can craft a 23-byte ICO file with a data_size value of approximately 4GB, causing memory exhaustion and worker crashes without requiring authentication.

Detection Guidance

Detecting this vulnerability requires monitoring for imgproxy instances running versions before 4.0.16. Check running processes for imgproxy and verify version with 'imgproxy --version'. Inspect network traffic for ICO file processing requests. Monitor system logs for worker crashes or memory exhaustion errors.

Impact Analysis

This vulnerability can lead to denial-of-service conditions where the imgproxy service crashes due to excessive memory consumption. It may disrupt image processing operations, cause service unavailability, and require manual intervention to restart workers. No authentication is needed for exploitation, making it easier for attackers to target systems.

Mitigation Strategies

Upgrade imgproxy to version 4.0.16 or later immediately. If upgrading is not possible, disable ICO file processing in imgproxy configuration. Implement network-level restrictions to block untrusted ICO file uploads. Monitor system resources for signs of memory exhaustion.

Chat Assistant

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

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...