CVE-2026-67239

Description

A flaw was found in rabbitmq-server. The stream-management interface fails to properly sanitize peer certificate fields, leading to a stored Cross-Site Scripting (XSS) vulnerability. A remote attacker with a valid Transport Layer Security (TLS) certificate containing a crafted Distinguished Name (DN) can connect to a stream listener configured to verify peer certificates. When an administrator views the stream connection details in the management console, the malicious script executes in their browser, potentially allowing the attacker to perform unauthorized administrative actions or compromise the session.

Statement

This vulnerability is evaluated as having Moderate severity by Red Hat because exploitation demands significant prerequisites: both stream and stream-management plugins must be enabled, mutual TLS with client certificate verification must be active, and the attacker must hold a certificate signed by a trusted certificate authority. These features are not enabled concurrently in standard deployments. Furthermore, successful execution requires an administrator to actively inspect the specific stream connection details in the web interface, substantially reducing the likelihood of exposure.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.75.4N/A
Attack VectorNetworkNetworkN/A
Attack ComplexityHighLowN/A
Privileges RequiredNoneLowN/A
User InteractionRequiredRequiredN/A
ScopeChangedChangedN/A
ConfidentialityLowLowN/A
Integrity ImpactLowLowN/A
Availability ImpactNoneNoneN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

NVD: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Understanding the Weakness (CWE)

Access Control,Confidentiality

Technical Impact: Bypass Protection Mechanism; Read Application Data

The most common attack performed with cross-site scripting involves the disclosure of private information stored in user cookies, such as session information. Typically, a malicious user will craft a client-side script, which -- when parsed by a web browser -- performs some activity on behalf of the victim to an attacker-controlled system (such as sending all site cookies to a given E-mail address). This could be especially dangerous to the site if the victim has administrator privileges to manage that site. This script will be loaded and run by each user visiting the web site. Since the site requesting to run the script has access to the cookies in question, the malicious script does also.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

In some circumstances it may be possible to run arbitrary code on a victim's computer when cross-site scripting is combined with other flaws, for example, "drive-by hacking."

Confidentiality,Integrity,Availability,Access Control

Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism; Read Application Data

The consequence of an XSS attack is the same regardless of whether it is stored or reflected. The difference is in how the payload arrives at the server. XSS can cause a variety of problems for the end user that range in severity from an annoyance to complete account compromise. Some cross-site scripting vulnerabilities can be exploited to manipulate or steal cookies, create requests that can be mistaken for those of a valid user, compromise confidential information, or execute malicious code on the end user systems for a variety of nefarious purposes. Other damaging attacks include the disclosure of end user files, installation of Trojan horse programs, redirecting the user to some other page or site, running "Active X" controls (under Microsoft Internet Explorer) from sites that a user perceives as trustworthy, and modifying presentation of content.

Frequently Asked Questions

Want to get errata notifications? Sign up here.