CVE-2026-121714rabbitmq rabbitmq-server insufficient verification of data authenticity
CVE-2026-121714 is a insufficient verification of data authenticity in rabbitmq rabbitmq-server, rated medium (5.3 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
Data is accepted without proof it came from where it claims. Two components read the same input differently, and an attacker exploits the gap.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.
What an attacker gains
The scored direct impact on the component itself is low. In practice, this kind of flaw lets an attacker read or tamper with traffic, or pass a forged message as genuine. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade rabbitmq rabbitmq-server to 4.3.5 or later.
- Until it is patched, review who holds accounts that can reach it.
Description from NVD
RabbitMQ is a messaging and streaming broker. In the affected revision identified by the advisory, the AMQP 1.0 server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl stops at the first body section and preserves the remaining bytes in bare_and_footer without validating message-section order. An authenticated publisher with write permission can place a properties section carrying a forged user-id after the body, causing rabbit_access_control:check_user_id/2 to see no user-id while permissive downstream AMQP 1.0 decoders or AMQP 0-9-1 conversion through classic and quorum queues expose the forged identity. Applications that rely on RabbitMQ-validated user-id metadata can therefore accept attacker-controlled publisher attribution. Strict consumers that reject out-of-order sections are not vulnerable to identity spoofing, and the issue does not bypass broker routing or destination authorization. This issue is fixed in version 4.3.5.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- TLS termination and service-to-service channels. The flaw sits on the network path between clients and services.
- Signature checks. The flaw sits on the network path between clients and services.
- Proxies, load balancers and the servers behind them. The flaw sits between a front-end proxy and its back end.
- Interfaces that accept external input. The flaw sits at the input boundary of the affected component.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- On the network path between clients and services. An attacker who crosses it can read or tamper with traffic, or pass a forged message as genuine.
- Between a front-end proxy and its back end. An attacker who crosses it can smuggle requests past the proxy's checks.
Questions to answer about your own systems
- Where does rabbitmq rabbitmq-server run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
14-day free trial
Understand how your systems connect.
See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.
Read more
Patches and commits
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.