Answer in brief
CVE-2026-93561 records a Medium severity (CVSS 6.5) vulnerability in Io.netty/netty-codec-memcache: netty: memcache binary codec signed/unsigned type mismatch causes frame desynchronization and response smuggling. The current sources do not mark it as known exploited. The current feed maps Red Hat/jboss-eap-7/eap74-els-openjdk11-openshift-rhel8 (generic), Red Hat/jboss-eap-7/eap74-els-openjdk17-openshift-rhel8 (generic), Red Hat/jboss-eap-7/eap74-els-openjdk8-openshift-rhel8 (generic), Red Hat/netty-codec-memcache (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Red Hat/jboss-eap-7/eap74-els-openjdk11-openshift-rhel8 (generic), Red Hat/jboss-eap-7/eap74-els-openjdk17-openshift-rhel8 (generic), Red Hat/jboss-eap-7/eap74-els-openjdk8-openshift-rhel8 (generic), Red Hat/netty-codec-memcache (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Red Hat/jboss-eap-7/eap74-els-openjdk11-openshift-rhel8generic | * | Not reported |
| Red Hat/jboss-eap-7/eap74-els-openjdk17-openshift-rhel8generic | * | Not reported |
| Red Hat/jboss-eap-7/eap74-els-openjdk8-openshift-rhel8generic | * | Not reported |
| Red Hat/netty-codec-memcachegeneric | * | Not reported |
Published upstream
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.