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.
CVE-2026-93561
Score 6.5 from GitHub Security Advisory published 2026-09-18. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (1)
Auto-updated Sep 18, 20262536949 – (CVE-2026-93561) CVE-2026-93561 io.netty/netty-codec-memcache: Netty: Memcache binary codec signed/unsigned type mismatch causes frame desynchronization and response smuggling
https://bugzilla.redhat.com/show_bug.cgi?id=2536949Vendor Advisories for CVE-2026-93561(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 21:28 UTCEG score recompute
- 2026-09-18 21:28 UTCGHSA enrichment
- 2026-09-18 20:31 UTCEG score recompute
- 2026-09-18 20:31 UTCGHSA enrichment
- 2026-09-18 19:08 UTCEG score recompute
- 2026-09-18 19:08 UTCGHSA enrichment
- 2026-09-18 15:25 UTCEG score recompute
- 2026-09-18 15:25 UTCGHSA enrichment
- 2026-09-18 14:59 UTCEG score recompute
- 2026-09-18 14:59 UTCGHSA enrichment
- 2026-09-18 14:21 UTCEG score recompute
- 2026-09-18 14:21 UTCGHSA enrichment
- 2026-09-18 13:34 UTCGHSA enrichment
- 2026-09-18 13:29 UTCEG score recompute▲ 6.50
- 2026-09-18 13:29 UTCGHSA enrichment
- 2026-09-18 13:29 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
- 2026-09-18 11:19 UTCNVD update
- 2026-09-18 10:24 UTCEG score recompute
- 2026-09-18 10:24 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-93561?
When was CVE-2026-93561 disclosed?
What is the CVSS score of CVE-2026-93561?
How do I remediate CVE-2026-93561?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93561
Is Your Infrastructure Affected by CVE-2026-93561?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.