CVE-2026-67242: CWE-613: Insufficient Session Expiration in rabbitmq rabbitmq-server
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.
AI Analysis
Technical Summary
RabbitMQ's OAuth2 implementation in versions >=4.2.0 <4.2.9 and >=4.3.0 <4.3.3 improperly validates the token expiration claim (exp) when it is a JSON float. The functions validatetokenexpiry/1 and expirytimestamp/1 only check expiry if exp is an integer, ignoring float values. Consequently, if an Identity Provider emits exp as a float (allowed by RFC 7519), the token expiry validation is skipped, allowing acceptance of expired tokens and preventing session termination. This flaw is addressed in versions 4.2.9 and 4.3.3.
Potential Impact
An attacker with a previously valid signed token containing a float exp value can bypass token expiry checks, resulting in sessions that never expire or disconnect. This undermines session management and could allow unauthorized prolonged access. The vulnerability requires the OAuth2 backend and an IdP that emits float exp values, which is uncommon among mainstream IdPs.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 4.2.9 and 4.3.3. Users should upgrade to these or later versions to ensure proper token expiry validation. No additional mitigations are indicated by the vendor advisory.
CVE-2026-67242: CWE-613: Insufficient Session Expiration in rabbitmq rabbitmq-server
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.
CVSS v4.0
Score 6.3medium
Affected software
rabbitmq
rabbitmq-server
pkg:github/rabbitmq/rabbitmq-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ's OAuth2 implementation in versions >=4.2.0 <4.2.9 and >=4.3.0 <4.3.3 improperly validates the token expiration claim (exp) when it is a JSON float. The functions validatetokenexpiry/1 and expirytimestamp/1 only check expiry if exp is an integer, ignoring float values. Consequently, if an Identity Provider emits exp as a float (allowed by RFC 7519), the token expiry validation is skipped, allowing acceptance of expired tokens and preventing session termination. This flaw is addressed in versions 4.2.9 and 4.3.3.
Potential Impact
An attacker with a previously valid signed token containing a float exp value can bypass token expiry checks, resulting in sessions that never expire or disconnect. This undermines session management and could allow unauthorized prolonged access. The vulnerability requires the OAuth2 backend and an IdP that emits float exp values, which is uncommon among mainstream IdPs.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 4.2.9 and 4.3.3. Users should upgrade to these or later versions to ensure proper token expiry validation. No additional mitigations are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-28T19:50:39.439Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab6a25cf7a7c54106018e35
Added to database: 09/25/2026, 16:33:32 UTC
Last enriched: 09/25/2026, 16:48:29 UTC
Last updated: 09/26/2026, 02:44:56 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.