CVE-2026-93565VulnerabilityPublished 18 Sep 2026Updated 6 Nov 2026

Summary RtspMethods.valueOf() silently strips trailing control bytes (any character with code point <= 0x20, the full

Source GCVE Database

Compare

Authoritative record:CVE-2026-93565· High 7.5

Not known to be exploited · CVSS 7.5 High : patch Red Hat Build of Apache Camel 3.33.3.SP2 soon.

Data as of 6 Nov 2026, 13:49 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-6f4p-h3xm-c8rc

What to do

Patches and advisories

Affected software

Product	Affected	Fixed in
Red Hat Build of Apache Camel 3.33.3.SP2io.netty/netty-codec-http	Affected–	Fixed in–
Red Hat Build of Debezium 3.6netty-codec-http	Affected–	Fixed in–
Red Hat build of Keycloak 26.4keycloak-rhel9-container	Affected–	Fixed in–
Red Hat build of Keycloak 26.4keycloak-rhel9-operator-bundle-container	Affected–	Fixed in–
Red Hat build of Keycloak 26.4keycloak-rhel9-operator-container	Affected–	Fixed in–
Red Hat build of Keycloak 26.6.8netty-codec-http	Affected–	Fixed in–

AI-suggested

A fix is available as indicated by the Red Hat advisory for Red Hat build of Quarkus 3.33.3.SP2 and related updates. Users should apply the official security updates provided by their vendor to address this issue. No additional mitigation steps are required beyond applying the vendor's patch.

Description

The vulnerability in RtspMethods.valueOf() causes it to silently strip trailing control bytes (characters with code point <= 0x20) before cache lookup. This allows an RTSP request method token with trailing control bytes, such as PLAY\x00 or PLAY\r, to be interpreted as a valid PLAY request, making the application unable to distinguish it from a clean request. This flaw is similar to previously fixed issues in related components but was not addressed in RtspMethods.valueOf().

Impact

An attacker can send RTSP requests with method tokens that include trailing control bytes, which are silently stripped by RtspMethods.valueOf(), causing the server to treat these malformed requests as valid. This can lead to authorization bypass or other logic errors at the application layer since the request is accepted as legitimate despite the trailing control bytes. The CVSS vector indicates no confidentiality or availability impact but a high impact on integrity.

Summary

RtspMethods.valueOf() in Netty-based RTSP servers removes trailing control bytes from method tokens before performing a cache lookup against predefined method constants. As a result, an RTSP request with a method token ending in trailing control bytes (e.g., PLAY\x00 or PLAY\r) is decoded as a successful PLAY request, with the same object reference as the cached singleton. This means the application layer cannot differentiate between a clean method token and one with trailing control bytes. The root cause is the independent checkNonEmptyAfterTrim() call in RtspMethods.valueOf(), which allows the cache lookup to occur before the hardened HttpMethod constructor sees the token. This vulnerability is related to CVE-2026-93565 and has a CVSS score of 7.5 (high severity).

References

Community reviews

Loading reviews…