ETK-2026-3126Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
go:github.com/imgproxy/imgproxy/v3 >= 4.0.0, < 4.0.16
fixed in 4.0.16
ETK-2026-3126Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:golang/github.com/imgproxy/imgproxy/v3
pkg:golang/github.com/imgproxy/imgproxy/v2
pkg:golang/github.com/imgproxy/imgproxy
3h 01msince last run
27mAI analysisAnalysis: how long the AI spent reversing this signal.
description
imgproxy versions before 4.0.16 can mishandle size values while loading ICO images, leading to heap corruption. An attacker who can cause the service to process a crafted ICO file may crash the process or potentially execute code.
mitigation
Upgrade imgproxy to version 4.0.16 or later. Until upgrades are complete, prevent processing of untrusted ICO files.
fixed in 4.0.16
check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
27m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–
outcome
No artifact: an exploit or check was attempted but could not be produced at this moment.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-30 22:57Zghsa: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/ETK-2026-3126
{ "etk_id": "ETK-2026-3126", "cve_id": null, "display_id": "ETK-2026-3126", "ghsa_id": "GHSA-hff9-5pqw-6w9f", "euvd_id": null, "status": "published", "anchor_state": "awaiting_cve", "title": "Integer-overflow heap overflow in imgproxy ICO loader", "summary": "imgproxy versions before 4.0.16 can mishandle size values while loading ICO images, leading to heap corruption. An attacker who can cause the service to process a crafted ICO file may crash the process or potentially execute code.", "mitigation": "Upgrade imgproxy to version 4.0.16 or later. Until upgrades are complete, prevent processing of untrusted ICO files.", "vendor": "go", "product": "go:github.com/imgproxy/imgproxy/v3", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 4.0.0, < 4.0.16" ], "ecosystem": "go", "fixed_versions": [ "4.0.16" ], "package_name": "github.com/imgproxy/imgproxy/v3", "purl": "pkg:golang/github.com/imgproxy/imgproxy/v3" }, { "affected_notes": [], "affected_ranges": [ ">= 4.0.0, < 4.0.16" ], "ecosystem": "go", "fixed_versions": [ "4.0.16" ], "package_name": "github.com/imgproxy/imgproxy/v2", "purl": "pkg:golang/github.com/imgproxy/imgproxy/v2" }, { "affected_notes": [], "affected_ranges": [ ">= 4.0.0, < 4.0.16" ], "ecosystem": "go", "fixed_versions": [ "4.0.16" ], "package_name": "github.com/imgproxy/imgproxy", "purl": "pkg:golang/github.com/imgproxy/imgproxy" } ], "cwes": null, "cvss_score": 9.8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "deterministic", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 27.1920194, "t0_at": null, "signals": { "trigger_signal": { "at": "2026-10-30T22:57:00+00:00", "days": -0.12678487201388888, "is_lower_bound": true, "measured_at": "2026-10-31T01:59:34.243441+00:00", "url": "https://github.com/advisories/GHSA-hff9-5pqw-6w9f" } } }
published 2026-10-30 23:27Z
last change 2026-10-31 01:48Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.