{"id":"CVE-2026-93561","title":"A flaw was found in io.netty/netty-codec-memcache","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 ca…","severity":"medium","cvss":6.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","cwe":["CWE-1035"],"vendor":"Red Hat","product":"netty-codec-memcache","affected":["netty-codec-memcache (all versions)","netty-codec-memcache (all versions)","jboss-eap-7/eap74-els-openjdk11-openshift-rhel8 (all versions)","jboss-eap-7/eap74-els-openjdk17-openshift-rhel8 (all versions)","jboss-eap-7/eap74-els-openjdk8-openshift-rhel8 (all versions)","netty-codec-memcache (all versions)","netty-codec-memcache (all versions)"],"published":"2026-09-18","updated":"2026-09-18","sourceUpdated":"2026-09-18T21:18:46.847","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-93561","references":[{"url":"https://access.redhat.com/security/cve/CVE-2026-93561","label":"secalert@redhat.com"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2536949","label":"secalert@redhat.com"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2536949","label":"134c704f-9b21-4f2e-91b3-4a467353bcc0"},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-93561.json"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93561"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93561"}],"tags":["nvd","cve.org","csaf","vex","red-hat"],"ssvc":{"exploitation":"none","automatable":"yes","technicalImpact":"partial","timestamp":"2026-09-18T14:48:56.320115Z"},"ingestedAt":"2026-09-18T10:39:24.460Z","epss":0.00175,"epssPercentile":0.07234,"slug":"CVE-2026-93561","body":"## Overview\n\nA 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.\n\n## Vendor advisories\n\n- **Red Hat VEX** · Important · affected: Red Hat build of Apache Camel for Spring Boot 4, Red Hat Fuse 7, Red Hat JBoss Enterprise Application Platform 7, Red Hat Single Sign-On 7 · no fix planned: Red Hat build of Apache Camel for Spring Boot 4, Red Hat Fuse 7, Red Hat JBoss Enterprise Application Platform 7, Red Hat Single Sign-On 7 · updated 2026-09-18 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-93561.json)","depth":"sunlit","depthScore":36,"depthScoreParts":{"impact":35.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[{"seq":206834,"id":"CVE-2026-93561","ts":1789738971953,"field":"cvss","old":null,"new":"6.5"},{"seq":206833,"id":"CVE-2026-93561","ts":1789738971953,"field":"severity","old":"none","new":"medium"}]}