Skip to main content
VulnerabilityPublished

CVE-2026-121714: rabbitmq-server · Improper Input Validation

Affects rabbitmq-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.3.5 when convenient.

Data as of 20 Nov 2026, 20:14 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.05.3
Patch
Available – fixed in 4.3.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 20 Nov 2026.

What to do

Upgrade rabbitmq-server to 4.3.5.

Affected software

ProductAffectedFixed in
rabbitmqrabbitmq-serverAffected
  • >=4.3.0 <4.3.5
Fixed in
  • 4.3.5

AI-suggested

Upgrade RabbitMQ server to version 4.3.5 or later, where this vulnerability is fixed. Until then, applications should consider using strict consumers that reject out-of-order message sections to avoid identity spoofing. No other immediate actions are indicated by the vendor advisory.

Description

CVE-2026-121714 is a medium severity vulnerability in RabbitMQ server versions 4.3.0 up to but not including 4.3.5. It involves improper input validation in the AMQP 1.0 server_mode parser, allowing an authenticated publisher with write permission to spoof user identity metadata by placing a forged user-id in a message section after the body. This can lead to applications accepting attacker-controlled publisher attribution. The issue does not affect broker routing or authorization and is fixed in version 4.3.5.

References

Community reviews

Loading reviews…