Skip to main content
cve.nowby Sazabi
← Vulnerabilities
GO-2026-6898GHSA-MMQ5-XM89-9PFG

imgproxy has unbounded memory allocation in ICO loader that allows unauthenticated memory-exhaustion DoS via crafted data_size field in…

Exploited
No known exploitation
Fix
Fixed in 4.0.16
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.0.16.

Published
Last modified
10/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

imgproxy, an image processing server, is affected by a flaw in its ICO image loader that lets an attacker exhaust server memory with a crafted file that declares an oversized data_size field, causing denial of service. The description does not state how the attacker reaches the vulnerable code, so the access path is not specified.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

imgproxy has unbounded memory allocation in ICO loader that allows unauthenticated memory-exhaustion DoS via crafted data_size field in github.com/imgproxy/imgproxy

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects Go packages
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

How the score works · Leaderboard

What to do

  • Upgrade to a fixed version: 4.0.16.

Timeline

  1. Advisory published
  2. Record last updated
  3. First seen by cve.now

Affected versions

  • github.com/imgproxy/imgproxyGo

    All versions

  • github.com/imgproxy/imgproxy/v2Go

    All versions

  • github.com/imgproxy/imgproxy/v3Go

    From 3.3.0

  • github.com/imgproxy/imgproxy/v4Go

    fixed in 4.0.16

Evidence 3

  1. Advisory
  2. Patch
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about GO-2026-6898

Is GO-2026-6898 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by GO-2026-6898?

github.com/imgproxy/imgproxy (Go): all versions. github.com/imgproxy/imgproxy/v2 (Go): all versions. github.com/imgproxy/imgproxy/v3 (Go): from 3.3.0. github.com/imgproxy/imgproxy/v4 (Go): before 4.0.16.Source: cve.now feed data

How do I fix GO-2026-6898?

Upgrade to a fixed version: 4.0.16.Source: cve.now feed data

Sources

More vulnerabilities