Vulnerability Details CVE-2026-67242
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.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.003
EPSS Ranking 26.4%
CVSS Severity
CVSS v3 Score 5.4
Products affected by CVE-2026-67242
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.0
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.1
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.2
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.3
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.4
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.5
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.6
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.7
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.8
-
cpe:2.3:a:broadcom:rabbitmq_server:4.3.0
-
cpe:2.3:a:broadcom:rabbitmq_server:4.3.1
-
cpe:2.3:a:broadcom:rabbitmq_server:4.3.2