Insufficient Session Expiration Affecting rabbitmq-server package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.35% (27th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-RABBITMQSERVER-20163552
  • published27 Sept 2026
  • disclosed25 Sept 2026

Introduced: 25 Sep 2026

NewCVE-2026-67242  (opens in a new tab)
CWE-613  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 rabbitmq-server.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rabbitmq-server package and not the rabbitmq-server package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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 Base Scores

version 3.1