CVE-2026-67237 rabbitmq CVE debrief

Who should care

Defenders managing RabbitMQ instances with management.oauth_enabled set to true should verify their configurations to prevent potential JavaScript injection attacks. Operators of RabbitMQ instances, platform administrators, and security teams should review their systems for exposure and apply patches or mitigations as necessary. Vulnerability management and security teams should prioritize verifying RabbitMQ versions and configurations to ensure they are 4

Why it matters

CVE-2026-67237 allows attacker-controlled token content to execute JavaScript in the RabbitMQ management UI. Defenders should verify RabbitMQ versions and configurations to prevent potential JavaScript injection attacks.

• Potential JavaScript execution in management UI
• Required verification of RabbitMQ versions and configurations
• Possible exposure through cookie path

Technical summary

RabbitMQ versions 4.2.0 to 4.2.8 and 4.3.2 are vulnerable to JavaScript injection via the management UI. The vulnerability arises from improper escaping of bearer tokens in OAuth bootstrap JavaScript. Attackers can inject JavaScript into the management UI by manipulating the Authorization header or access_token cookie. This issue is fixed in versions 4.2.8 and 4.3.2. Defenders should prioritize verifying RabbitMQ versions and configurations to prevent potential JavaScript injection attacks. The endpoint is exposed before authentication only when management.oauth_enabled is true.

Defensive priority

Defenders should prioritize verifying RabbitMQ versions and configurations.

Recommended defensive actions

• Verify RabbitMQ version and apply patches
• Review management.oauth_enabled configuration
• Monitor for suspicious activity
• Confirm whether affected RabbitMQ instances exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the RabbitMQ vulnerability. Evidence is limited to public CVE and NVD records. Defenders should verify RabbitMQ versions and configurations to ensure they are not exposed. The CVE record was published on 2026-09-25T17:17:11.883Z and has not been modified since then. No additional evidence is available beyond these public records.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.