Skip to main content
No exploitation reportedFix available

CVE-2026-67234

No exploitation reported by the sources we read.

  • Published2026-09-25
  • Fixed in4.3.2 · 4.2.8
  • WeaknessCWE-20

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, get_auth_mechanism/1 used term_to_binary/1 on the strict_auth_mechanism or preferred_auth_mechanism atom when clearing the corresponding cookie, producing a non-ASCII cookie name that violates RFC 6265 and can prevent the browser from deleting the preference. The issue is not directly exploitable for code execution or data exfiltration; its security relevance is limited to stale authentication-mechanism preferences persisting across logout and login cycles. This issue is fixed in versions 4.2.8 and 4.3.2.

Timeline

dates in UTC
  1. 2026-09-2517:17CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-67234?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-67234?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Broadcom rabbitmq server
BranchAffectedFixed in
4.3≥ 4.3.0, < 4.3.24.3.2
4.2≥ 4.2.0, < 4.2.84.2.8

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2026-67234 Red Hat Product Security3 products fixed · 8 known affected

    rabbitmq-server: rabbitmq-server: Authentication preference persistence via invalid cookie name

    rabbitmq-server4.2.src as a component of Red Hat Hardened Images · rabbitmq-server as a component of Red Hat OpenStack Platform 13 (Queens) · rabbitmq-server.src as a component of Red Hat OpenStack Platform 13 (Queens) · +5 more

  • RHSA-2026:67552 Red Hat Product Security3 products fixed

    Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

Full record on NVD

Fix

  1. Update Broadcom rabbitmq server to 4.3.2 · 4.2.8
  2. Vendor fix Red Hat Product Security CVE-2026-67234 · 3 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
  3. No fix available, says the vendor Red Hat Product Security CVE-2026-67234 · 2 productsFix deferred
  4. No fix planned, says the vendor Red Hat Product Security CVE-2026-67234 · 6 productsOut of support scope

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2026-09-25
  • OpenCVESSVC decisionnone—
  • CNACVSS 4.02.3read 2026-10-23
  • NVDCVSS 3.14.3read 2026-10-23
  • CNAweakness (CWE)CWE-20read 2026-10-23
  • FIRST EPSSEPSS score0.4 %2026-10-22
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-09-25
Last Modified
2026-10-20
NVD status
Analyzed

Frequently asked questions

What is CVE-2026-67234?

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, get_auth_mechanism/1 used term_to_binary/1 on the strict_auth_mechanism or preferred_auth_mechanism atom when clearing the corresponding cookie, producing a non-ASCII cookie name that violates RFC 6265 and can prevent the browser from deleting the preference. The issue is not directly exploitable for code execution or data exfiltration; its security relevance is limited to stale authentication-mechanism preferences persisting across logout and login cycles. This issue is fixed in versions 4.2.8 and 4.3.2.

Is CVE-2026-67234 actively exploited?

Active exploitation of CVE-2026-67234 has not been confirmed. Its EPSS score was 0.4% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-67234?

CVE-2026-67234 has a CVSS v3 base score of 4.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N.

Running rabbitmq? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database