All reports
Medium

rabbitmq-server: rabbitmq-server: Authentication bypass via improper validation of floating-point token expiration timestamps

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-67242

Probability of exploitation in the next 30 days: 0.35%

FIRST EPSS · 2026-11-21

Description

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.

A flaw was found in rabbitmq-server. When configured to use OAuth 2.0 authentication, the server does not properly validate token expiration timestamps that are represented as floating-point numbers. A remote attacker with an expired token can exploit this issue to bypass expiration checks, gaining unauthorized access or maintaining active connections indefinitely.