CVE-2026-93561 json
Io.netty/netty-codec-memcache: netty: memcache binary codec signed/unsigned type mismatch causes frame desynchronization and response smuggling
published 2026-09-18 51 d ago modified 2026-09-25 44 d ago also EUVD-2026-82864
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
A flaw was found in io.netty/netty-codec-memcache. The Memcache binary protocol codec incorrectly reads `keyLength` and `extrasLength` as signed Java types instead of unsigned, as specified by the protocol. A malicious Memcache server can exploit this type mismatch by sending a specially crafted response. This can lead to frame desynchronization and response smuggling, where one client's data may be inadvertently exposed to another client's response stream in proxy or cache environments.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-93561 updated cvss 6.5
io.netty/netty-codec-memcache: Netty: Memcache binary codec signed/unsigned type mismatch causes frame desynchronization and response smuggling
-
Red Hat build of Apache Camel for Spring Boot 4 netty-codec-memcache 4.1.136.Final-redhat-00001affected: workaround, no fix available “See https://github.com/netty/netty/security/advisories/GHSA-wxrh-4rgq-pjcg for fixed versions and remediation guidance.”
-
Red Hat JBoss Enterprise Application Platform 7 jboss-eap-7/eap74-els-openjdk8-openshift-rhel8, jboss-eap-7/eap74-els-openjdk11-openshift-rhel8, jboss-eap-7/eap74-els-openjdk17-openshift-rhel8, netty-codec-memcache 4.1.136.Final-redhat-00001 Red Hat Single Sign-On 7 netty-codec-memcache 4.1.136.Final-redhat-00001affected: workaround, no fix planned “See https://github.com/netty/netty/security/advisories/GHSA-wxrh-4rgq-pjcg for fixed versions and remediation guidance.”
-
Red Hat Fuse 7 netty-codec-memcache 4.1.136.Final-redhat-00001not affected: vulnerable code not in execute path
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 51 d ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=2536949 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected products
- Red Hat Red Hat build of Apache Camel for Spring Boot 4
- Red Hat Red Hat Fuse 7
- Red Hat Red Hat JBoss Enterprise Application Platform 7
- Red Hat Red Hat Single Sign-On 7
Classification
- Weakness
-
- CWE-1035 OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities
- Technology feeds
References
-
bugzilla.redhat.com
/show_bug.cgi?id=2536949
issue-tracking, exploit
-
access.redhat.com
/security/cve/CVE-2026-93561
vdb-entry
Sources
- CVE List CVE-2026-93561
- NVD CVE-2026-93561
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.