Io.netty/netty-codec-http: netty rtspdecoder method-token smuggling via trailing control byte (CVE-2026-93565)
Published Last modified Sources: SUSE, Red Hat, CVE.org, BSI
What is affected, what to do
A flaw was found in Netty RtspDecoder. The `RtspMethods.valueOf()` function incorrectly strips trailing control bytes from method tokens in Real-Time Streaming Protocol (RTSP) requests.
Update Red Hat Build of Apache Camel 3.33.3.SP2 to version 4.1.138.Final-redhat-00001.
- Affected
- Red Hat Build of Apache Camel 3.33.3.SP2
lt *..4.1.138.Final-redhat-00001
- Red Hat Build of Apache Camel 3.33.3.SP2
- Fixed in
- Red Hat Build of Apache Camel 3.33.3.SP2
4.1.138.Final-redhat-00001
- Red Hat Build of Apache Camel 3.33.3.SP2
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.5
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
7.5
CVSS v3
Severity High on the scale from 0 to 10.
Source: SUSE, Red Hat, CVE.org, BSI
0.8 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 55.3
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 89.94 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.5
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.8 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 55.3
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-1035
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A flaw was found in Netty RtspDecoder. The `RtspMethods.valueOf()` function incorrectly strips trailing control bytes from method tokens in Real-Time Streaming Protocol (RTSP) requests. A remote attacker can exploit this by sending a specially crafted RTSP request, leading to method-token smuggling. This vulnerability allows an attacker to bypass method-based access controls and can also be used to launder malicious requests through Netty-based RTSP proxies, making them appear legitimate to backend systems.
Source: suse_csaf, redhat_csaf, NVD (NIST), cvelistv5, BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Red Hat | Red Hat AMQ Broker 7 |
|
|
| Red Hat | Red Hat AMQ Clients |
|
|
| Red Hat | Red Hat Build of Apache Camel 3.33.3.SP2 |
|
|
| Red Hat | Red Hat build of Apache Camel 4 for Quarkus 3 |
|
|
| Red Hat | Red Hat build of Apache Camel for Spring Boot 4 |
|
|
| Red Hat | Red Hat build of Apicurio Registry 3 |
|
|
| Red Hat | Red Hat Build of Debezium 3.6 |
|
|
| Red Hat | Red Hat Build of Keycloak |
|
|
| Red Hat | Red Hat build of Quarkus 3.27.5.SP2 |
|
|
| Red Hat | Red Hat build of Quarkus 3.33.3.SP2 |
|
|
| Red Hat | Red Hat Data Grid 8 |
|
|
| Red Hat | Red Hat Fuse 7 |
|
|
| Red Hat | Red Hat JBoss Enterprise Application Platform 7 |
|
|
| Red Hat | Red Hat JBoss Enterprise Application Platform 8 |
|
|
| Red Hat | Red Hat Single Sign-On 7 |
|
|
| Open Source | Netty |
|
|
Vendors and products
- Open Source Netty
- Red Hat Red Hat Amq Broker 7
- Red Hat Red Hat Amq Clients
- Red Hat Red Hat Build Of Apache Camel 3.33.3.sp2
- Red Hat Red Hat Build Of Apache Camel 4 For Quarkus 3
- Red Hat Red Hat Build Of Apache Camel For Spring Boot 4
- Red Hat Red Hat Build Of Apicurio Registry 3
- Red Hat Red Hat Build Of Debezium 3.6
- Red Hat Red Hat Build Of Keycloak
- Red Hat Red Hat Build Of Quarkus 3.27.5.sp2
- Red Hat Red Hat Build Of Quarkus 3.33.3.sp2
- Red Hat Red Hat Data Grid 8
Weakness classes (CWE)
CWE-1035OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities
Category
Entry at MITRE CWE-1035
References & sources
- access.redhat.comsecurity/cve/CVE-2026-93565Vulnerability database, x_refsource_REDHAT
- bugzilla.redhat.comRHBZ#2536952Issue tracking, x_refsource_REDHAT
- access.redhat.comRHSA-2026:69470Vendor advisory, x_refsource_REDHAT
- access.redhat.comRHSA-2026:69440Vendor advisory, x_refsource_REDHAT
- access.redhat.comRHSA-2026:70257Vendor advisory, x_refsource_REDHAT
- access.redhat.comRHSA-2026:83612Vendor advisory, x_refsource_REDHAT
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedRed Hat
New references:Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/93xxx/CVE-2026-93565.json">CVE-2026-93565</a>Reference added —https://access.redhat.com/errata/RHSA-2026:83612Source identifier: secalert@redhat.com
Record modifiedRed Hat
1 individual change: Affected versions (publisher)
Show the original change
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/93xxx/CVE-2026-93565.json">CVE-2026-93565</a>Source identifier: secalert@redhat.com
Record modifiedRed Hat
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://access.redhat.com/errata/RHSA-2026:69440Reference added —https://access.redhat.com/errata/RHSA-2026:70257Source identifier: secalert@redhat.com
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: yes
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-93565","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-09-21T19:48:34.585168Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Record modifiedRed Hat
New references:Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/93xxx/CVE-2026-93565.json">CVE-2026-93565</a>Reference added —https://access.redhat.com/errata/RHSA-2026:69470Source identifier: secalert@redhat.com
Show 2 older changes
Record modifiedRed Hat
Description added or changed
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Description changed ### Summary `RtspMethods.valueOf()` silently strips trailing control bytes (any character with code point <= 0x20, the full range that `String.trim()` removes) before performing a cache lookup against its ten pre-populated method constants. A wire-delivered RTSP request whose method token ends with a trailing control byte — for example `PLAY\x00` or `PLAY\r`, immediately before the separating space — is decoded by `RtspDecoder` as a fully successful PLAY request, with `decoderResult().isSuccess() == true and request.method() == RtspMethods.PLAY` (same object reference as the cached singleton). The application layer cannot distinguish this from a clean `PLAY` request. This is the same root cause as #16723 and #16971, in a sibling that those fixes did not reach. The fix for `HttpMethod` hardened `HttpMethod.valueOf()` directly, but `RtspMethods.valueOf()` has its own independent `checkNonEmptyAfterTrim()` call that runs before the cache lookup — meaning a trailing-control-byte token hits the cache before the hardened `HttpMethod` constructor ever sees it. ### Reproduction Minimal wire-level reproduction Send the following raw bytes to any Netty-based RTSP server using RA flaw was found in Netty RtspDecoder. The `RtspMethods.valueOf()` function incorrectly strips trailing control bytes from method tokens in Real-Time Streaming Protocol (RTSP) requests. A remote attacker can exploit this by sending a specially crafted RTSP request, leading to method-token smuggling. This vulnerability allows an attacker to bypass method-based access controls and can also be used to launder malicious requests through Netty-based RTSP proxies, making them appear legitimate to backend systems.Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/93xxx/CVE-2026-93565.json">CVE-2026-93565</a>Source identifier: secalert@redhat.com
ReceivedRed Hat
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness type: CWE-1035
Description added or changed
Show 6 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —### Summary `RtspMethods.valueOf()` silently strips trailing control bytes (any character with code point <= 0x20, the full range that `String.trim()` removes) before performing a cache lookup against its ten pre-populated method constants. A wire-delivered RTSP request whose method token ends with a trailing control byte — for example `PLAY\x00` or `PLAY\r`, immediately before the separating space — is decoded by `RtspDecoder` as a fully successful PLAY request, with `decoderResult().isSuccess() == true and request.method() == RtspMethods.PLAY` (same object reference as the cached singleton). The application layer cannot distinguish this from a clean `PLAY` request. This is the same root cause as #16723 and #16971, in a sibling that those fixes did not reach. The fix for `HttpMethod` hardened `HttpMethod.valueOf()` directly, but `RtspMethods.valueOf()` has its own independent `checkNonEmptyAfterTrim()` call that runs before the cache lookup — meaning a trailing-control-byte token hits the cache before the hardened `HttpMethod` constructor ever sees it. ### Reproduction Minimal wire-level reproduction Send the following raw bytes to any Netty-based RTSP server using RCVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NWeakness type (CWE) added —CWE-1035Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/93xxx/CVE-2026-93565.json">CVE-2026-93565</a>Reference added —https://access.redhat.com/security/cve/CVE-2026-93565Reference added —https://bugzilla.redhat.com/show_bug.cgi?id=2536952Source identifier: secalert@redhat.com
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-93565"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-93565.svg?lang=en" alt="CVE-2026-93565 – NEOSEC Intel" height="20"></a>