ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-mmq5-xm89-9pfg

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

Published Oct 30, 2026 · catalog updated Nov 5, 2026 · imgproxy has unbounded memory

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-mmq5-xm89-9pfg. A missing EPSS score is not a low risk. Compare imgproxy has unbounded memory with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (imgproxy has unbounded memory).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
Go github.com/imgproxy/imgproxy/v3

### Summary Unbounded and unvalidated memory allocation in imgproxy's ICO loader ( ). An attacker-controlled field (u32) from the ICO directory entry is passed directly to without any bounds check, so a single crafted 23-byte ICO file makes an imgproxy worker attempt a ~4GB allocation. Present in the latest release (v4.0.15) and the 3.3.x series; confirmed on a live production deployment of imgproxy v4.0.15. ### Details In in , the selected directory entry's is read and used directly for the allocation: There is no validation that is sane nor any check that the file actually contains bytes at the declared . A crafted 23-byte ICO whose directory entry declares (~4GB) drives . ### PoC ### Impact Unauthenticated network DoS / memory-exhaustion: on memory-constrained workers, a crash per crafted request. On larger hosts, ~4GB transient allocation per request (sustained firing exhausts memory or the allocation budget). Any imgproxy deployment that processes attacker-supplied images.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/imgproxy/imgproxy/v33.3.0 → 4.0.16

How to fix GHSA-mmq5-xm89-9pfg

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-mmq5-xm89-9pfg. A missing EPSS score is not a low risk. Compare imgproxy has unbounded memory with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 3.3.0 → 4.0.16. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-400: Uncontrolled Resource Consumption. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 30, 2026 · GitHub Advisory Database

    Detected

    ### Summary Unbounded and unvalidated memory allocation in imgproxy's ICO loader ( ). An attacker-controlled field (u32) from the ICO directory entry is passed directly to without any bounds check, so a single crafted 23-byte ICO file makes an imgproxy worker attempt a ~4GB allocation. Present in the latest release (v4.0.15) and the 3.3.x series; confirmed on a live production deployment of imgpro

  2. Oct 30, 2026 · GitHub Advisory Database

    Fix available

    github.com/imgproxy/imgproxy/v3 fixed in 4.0.16

  3. Oct 30, 2026 · GitHub Advisory Database

    Fix available

    github.com/imgproxy/imgproxy/v3 fixed in 4.0.16

  4. Oct 30, 2026 · GitHub Advisory Database

    Updated

    ### Summary Unbounded and unvalidated memory allocation in imgproxy's ICO loader ( ). An attacker-controlled field (u32) from the ICO directory entry is passed directly to without any bounds check, so a single crafted 23-byte ICO file makes an imgproxy worker attempt a ~4GB allocation. Present in the latest release (v4.0.15) and the 3.3.x series; confirmed on a live production deployment of imgpro

  5. Nov 5, 2026 · Go Vulnerability Database

    Updated

    ### Summary Unbounded and unvalidated memory allocation in imgproxy's ICO loader ( ). An attacker-controlled field (u32) from the ICO directory entry is passed directly to without any bounds check, so a single crafted 23-byte ICO file makes an imgproxy worker attempt a ~4GB allocation. Present in the latest release (v4.0.15) and the 3.3.x series; confirmed on a live production deployment of imgpro

Sources

  • GitHub Advisory DatabasePackage advisoryGHSA-mmq5-xm89-9pfg

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • Go Vulnerability DatabasePackage advisoryGHSA-mmq5-xm89-9pfg

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

    osv.dev
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-mmq5-xm89-9pfg

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

    osv.dev

References

Freshness

Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Go Vulnerability DatabaseNov 7, 2026
  • GitHub Advisory DatabaseNov 2, 2026
  • OpenSSF OSV / OSV ScannerNov 2, 2026