CVE-2026-93561
waiting for further signalsZero needs more public information before it can validate it.GHSA-7p33-hhxj-4qcr ↗EUVD-2026-82864 ↗
description
Netty's io.netty:netty-codec-memcache can parse certain Memcache binary response length fields incorrectly, causing subsequent response data to be associated with the wrong frame. A malicious Memcache server may exploit this to expose one client's response data to another in applications using shared proxy or cache connections; receiving responses from such a server is the relevant precondition.
mitigation
Upgrade io.netty:netty-codec-memcache to 4.2.18.Final or 4.1.138.Final, as applicable. Until upgraded, restrict Memcache backend connections to trusted servers and isolate client response streams where possible.
fixed in 4.2.18.Final, 4.1.138.Final
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-09-18 10:02Zghsa: trigger signal, started the run
- 2026-09-18 10:02Zcve.org record for CVE-2026-93561
this entry in the feed
GET /api/v1/feed/CVE-2026-93561
{ "etk_id": "ETK-2026-2446", "cve_id": "CVE-2026-93561", "display_id": "CVE-2026-93561", "ghsa_id": "GHSA-7p33-hhxj-4qcr", "euvd_id": "EUVD-2026-82864", "status": "published", "anchor_state": "anchored", "title": "Response smuggling in Netty Memcache codec", "summary": "Netty's `io.netty:netty-codec-memcache` can parse certain Memcache binary response length fields incorrectly, causing subsequent response data to be associated with the wrong frame. A malicious Memcache server may exploit this to expose one client's response data to another in applications using shared proxy or cache connections; receiving responses from such a server is the relevant precondition.", "mitigation": "Upgrade `io.netty:netty-codec-memcache` to 4.2.18.Final or 4.1.138.Final, as applicable. Until upgraded, restrict Memcache backend connections to trusted servers and isolate client response streams where possible.", "vendor": "maven", "product": "maven:io.netty:netty-codec-memcache", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 4.2.0.Final, <= 4.2.17.Final" ], "ecosystem": "maven", "fixed_versions": [ "4.2.18.Final" ], "package_name": "io.netty:netty-codec-memcache", "purl": "pkg:maven/io.netty/netty-codec-memcache" }, { "affected_notes": [], "affected_ranges": [ "<=4.1.137.Final" ], "ecosystem": "maven", "fixed_versions": [ "4.1.138.Final" ], "package_name": "io.netty:netty-codec-memcache", "purl": "pkg:maven/io.netty/netty-codec-memcache" } ], "cwes": [ 195 ], "cvss_score": 6.5, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 11.9663214, "t0_at": "2026-09-18T10:02:36.581000+00:00", "signals": { "trigger_signal": { "at": "2026-09-18T10:02:36.581000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-09-18T10:02:36.581000+00:00", "url": "https://github.com/netty/netty/security/advisories/GHSA-wxrh-4rgq-pjcg" } } }
published 2026-10-22 13:56Z
last change 2026-10-22 15:59Z
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.