imgproxy has out-of-bounds heap read/write in ICO loader BMP header reconstruction that allows unauthenticated remote worker crash
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/imgproxy/imgproxy/v3 4.0.17), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/imgproxy/imgproxy/v3
- Affected
- >= 3.3.0, < 4.0.17
- Fixed in
- 4.0.17
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-494m-4556-wf5p lists affected ranges: Go github.com/imgproxy/imgproxy/v3 >=3.3.0 <4.0.17
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-494m-4556-wf5p lists affected ranges: Go github.com/imgproxy/imgproxy/v3 >=3.3.0 <4.0.17 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Summary Out-of-bounds heap write in imgproxy's ICO loader (`vips/icoload.c`): when the ICO entry's image data buffer is small, the loader's BMP-header-reconstruction writes land past the allocation, corrupting the size field of the following heap chunk. The worker then aborts deterministically (glibc `munmap_chunk(): invalid pointer` → SIGABRT → Go panic, exit code 2).
Details In `vips_foreign_load_ico_header` in `vips/icoload.c`, after the ICO entry's image data is read into a heap buffer of `data_size + 14` bytes, the loader reconstructs a BMP file header in front of it using fields read from the ICO's internal BITMAPINFOHEADER: ``` uint32_t num_colors = GUINT32_FROM_LE(*(uint32_t *) (actual_data + 32)); // unvalidated uint16_t bpp = GUINT16_FROM_LE(*(uint16_t *) (actual_data + 14)); // unvalidated ``` ``` if ((num_colors == 0) && (bpp > 1` and, in cgo thread arenas, the `NON_MAIN_ARENA` bit lands in the `IS_MMAPPED` position of the corrupted word such that the next…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-494m-4556-wf5p
- Revision 1 · created ·
Published from ghsa record GHSA-494m-4556-wf5p
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-494m-4556-wf5p Advisory: imgproxy has out-of-bounds heap read/write in ICO loader BMP header reconstruction that allows unauthenticated remote worker crash IDs: GHSA-494m-4556-wf5p Record: https://patchnext.com/advisories/ghsa-494m-4556-wf5p (revision 2, source checked 31 Oct 2026, 06:45 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/imgproxy/imgproxy/v3 4.0.17. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/imgproxy/imgproxy/v3: affected >= 3.3.0, < 4.0.17; fixed in 4.0.17 ## Suggested inspection (read-only) - Go github.com/imgproxy/imgproxy/v3: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/imgproxy/imgproxy/v3. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-494m-4556-wf5p (GitHub-reviewed advisory GHSA-494m-4556-wf5p lists affected ranges: Go github.com/imgproxy/imgproxy/v3 >=3.3.0 <4.0.17) - Verified: https://osv.dev/vulnerability/GHSA-494m-4556-wf5p (OSV record GHSA-494m-4556-wf5p lists affected ranges: Go github.com/imgproxy/imgproxy/v3 >=3.3.0 <4.0.17 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…