Quick answers
- Is CVE-2026-123614 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123614 being exploited in the wild.
- How severe is CVE-2026-123614?
- Critical severity, with a CVSS score of 9.8, published 8 November 2026.
- Which products and versions are affected?
- Imgproxy 4.0.0 through 4.0.15.
- Is there a fix for CVE-2026-123614?
- Yes: fixed in 4.0.16. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123614 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-123614?
- Check whether you run Imgproxy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.0.16
Technical details
An integer overflow in vips/icoload.c occurs when allocating memory for ICO image data: the code adds a 32-bit attacker-controlled data_size to BMP_FILE_HEADER_LEN (14 bytes) without checking for overflow, causing the allocation to wrap. This results in a heap buffer overflow when subsequent read operations write beyond the undersized allocation, enabling denial of service or code execution via heap corruption. The vulnerability requires only network access and no authentication or user interaction.
Affected products
- imgproxy imgproxy 4.0.0 through 4.0.15
Timeline
- 2026-10-06: disclosed
- 2026-11-08: advisory