Skip to content
Threat Feed
low advisory

imgproxy: Unbounded memory allocation in ICO loader (CVE-2026-123616)

An unauthenticated attacker can exploit an unbounded memory allocation vulnerability in the imgproxy ICO loader to trigger process crashes and denial-of-service via malformed file uploads.

CVE search metadata

CVE search record: CVE-2026-123616. Severity: high. CVSS: 7.5. KEV: no. Product: imgproxy (>= 3.3.0, < 4.0.16). Brief: imgproxy: Unbounded memory allocation in ICO loader (CVE-2026-123616). Brief link: https://feed.craftedsignal.io/briefs/2026-11-imgproxy-memory-exhaustion/

Triage facts

Revision 1
Applicability
imgproxy (>= 3.3.0, < 4.0.16)
Evidence
Unknown
Severity
Low
Action
Elevated
Sources
1 public source
Freshness
Revision 1Nov 8, 11:21 UTC
Vulnerabilities
1 CVE
Source quality
A1Likely

imgproxy versions 3.3.0 through 4.0.15 are affected by an unbounded memory allocation vulnerability (CVE-2026-123616) in the ICO image processing module. The loader fails to validate the data_size field in processed ICO files. An attacker can submit a crafted 23-byte ICO file specifying a data_size of approximately 4GB, causing the service to allocate excessive memory, leading to worker process exhaustion and crashes.

Impact

Successful exploitation results in a denial-of-service condition for the imgproxy instance by inducing memory exhaustion and crashing worker processes.

Recommendation

  • Upgrade imgproxy instances to version 4.0.16 or later to include the mandatory validation of the data_size field in the ICO loader.
  • Implement request body size limits at the load balancer or reverse proxy level (e.g., Nginx client_max_body_size) if immediate patching is not feasible, though this will not prevent the specific vulnerability if small-file payloads are allowed.
  • Monitor logs for repeated worker process restarts or high memory usage spikes correlated with image processing tasks.

Immediate actions

Patch imgproxy to 4.0.16 or later

IT Operations 48h

Threat Hunt

Identify repeated worker process crashes in application logs

T1499.001 medium medium confidence hunt now

Data: Application logs (stderr/stdout), Orchestrator restart events (e.g., Kubernetes OOMKilled events)

Mitigations

Upgrade to 4.0.16

immediate IT Operations

CVE-2026-123616