- Exploited
- No known exploitation
- Fix
- Fixed in 4.0.17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.0.17.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
imgproxy, an image processing server, has a flaw in how it rebuilds BMP headers while loading ICO images, which allows out-of-bounds reads and writes in heap memory. An attacker can crash the worker process by sending a crafted image, and no login is needed for this.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
imgproxy has out-of-bounds heap read/write in ICO loader BMP header reconstruction that allows unauthenticated remote worker crash in github.com/imgproxy/imgproxy
cve.now Index
- 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
What to do
Upgrade to a fixed version: 4.0.17.
Timeline
- Advisory published
- Record last updated
- 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.17
Evidence 4
- Advisory
- Patch
- Patch
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about GO-2026-6895
Is GO-2026-6895 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-6895?
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.17.Source: cve.now feed data
How do I fix GO-2026-6895?
Upgrade to a fixed version: 4.0.17.Source: cve.now feed data