Skip to content
Applications

CVE-2026-123615

8.7
High
EPSS 0.53%Patch available

Heap OOB read/write in imgproxy ICO loader allows remote crash (unauthenticated DoS).

exploited
No known exploitation not in CISA KEV as of our last sync
fix
Fixed in 4.0.17
likelihood
EPSS 0.53%top 55% of scored CVEs
Published 8 Nov 2026Analysed here 10 Nov 2026CVSS scored by the publisher (CNA)

do firstUpgrade to a fixed release: 4.0.17.

common questions

Is CVE-2026-123615 being exploited?

Not confirmed. CVE-2026-123615 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.53% probability of exploitation in the next 30 days.

How severe is CVE-2026-123615?

CVE-2026-123615 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-123615?

Yes. A fix has been recorded for CVE-2026-123615. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-123615 affect?

CVE-2026-123615 affects imgproxy < 4.0.17 (ICO loader), vips/icoload.c (vips_foreign_load_ico_header). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-123615?

Upgrade imgproxy to >= 4.0.17; block/scan untrusted ICO uploads.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
imgproxy < 4.0.17 (ICO loader)vips/icoload.c (vips_foreign_load_ico_header)
impact

Unauthenticated remote heap corruption via crafted ICO images causing worker crash and glibc abort (remote DoS); may corrupt heap metadata.

action required

Patch when possible

affected versions
imgproxy
  • affected>= 3.3.0 and < 4.0.17
vendor says fixed in4.0.17

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

timeline

  1. 8 Nov 2026Published
  2. 8 Nov 2026CVE record last updated · same day later
  3. 10 Nov 2026Analysed by vulneraibility.com · 3 days later

also known as

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
2 references in the CVE record: 2 advisories
  • Advisorygithub.com /imgproxy/imgproxy/security/advisories/GHSA-494m-4556-wf5p
  • Advisoryvulncheck.com /advisories/imgproxy-before-4.0.17-out-of-bounds-write-in-ico-loader

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • FIRST EPSS: exploit probability and percentile
  • OSV: advisory aliases and downstream package versions
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved