CVE-2026-67242: Rabbitmq Rabbitmq-Server

Medium severity, CVSS 6.3. EPSS: 0.5% chance of exploitation in the next 30 days.

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and 4.3.3, OAuth2 isinteger(Exp) guard skips token-expiry checks for float exp. validatetokenexpiry/1 (lines 208-214) and expirytimestamp/1 (138-144) both guard with 'when isinteger(Exp)' and fall through to ok/never for float values. josejwt:verify validates only the signature, not exp. With float exp, no expiry validation occurs anywhere in the If the IdP emits exp as a JSON float (RFC 7519 permits fractional NumericDate), both the login-time expiry check and the mid-connection disconnect timer are silently skipped , an already-expired token is accepted, and connections never time OAuth2 backend enabled IdP emits float exp (uncommon; mainstream IdPs emit integers) Attacker possesses a previously-valid signed. This issue is fixed in versions 4.2.9 and 4.3.3.

Affected products

• Rabbitmq Rabbitmq-Server: from 4.2.0, before 4.2.9 (fixed in 4.2.9); from 4.3.0, before 4.3.3 (fixed in 4.3.3)

Published 2026-09-25. Last modified 2026-09-28.