RabbitMQ: OAuth2 is_integer(Exp) guard skips token-expiry checks for float exp
rabbitmq-server
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| rabbitmq rabbitmq-server |
| No fix yet |
Original 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.
From the CVE record · GitHub_M
References
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-rrj4-g94f-rqj9Vendor advisory
- github.com/rabbitmq/rabbitmq-server/commit/d10a369a96658d0fba1050bd43c732e58fcf28fdPatch
- github.com/rabbitmq/rabbitmq-server/commit/f189a8824c9efbce46bd9438fcdbda4521cfc923Patch
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9Release notes
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3Release notes
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67242.json
- nvd.nist.gov/vuln/detail/CVE-2026-67242