VulnerabilityPublished 25 Sep 2026

CVE-2026-67242: rabbitmq-server · Insufficient Session Expiration

Affects rabbitmq-serverSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.3.3 or 4.2.9 when convenient.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 4.0 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.3.3, 4.2.9

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade rabbitmq-server and rabbitmq/rabbitmq-server to 4.3.3 or 4.2.9.

Affected software

Product	Affected	Fixed in
rabbitmqrabbitmq-server	Affected >=4.3.0 <4.3.3	Fixed in 4.3.3
rabbitmqrabbitmq-server	Affected >=4.2.0 <4.2.9	Fixed in 4.2.9
GitHubrabbitmq/rabbitmq-server`pkg:github/rabbitmq/rabbitmq-server`Other threats	Affected >=4.2.0 <4.2.9 >=4.3.0 <4.3.3	Fixed in 4.2.9 4.3.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in rabbitmq-server versions 4.2.9 and 4.3.3. Users should upgrade to at least these versions to remediate the issue. No other mitigations are indicated by the vendor advisory. Patch status is confirmed fixed in these versions.

Description

CVE-2026-67242 is a medium severity vulnerability in rabbitmq-server affecting versions from 4.2.0 up to but not including 4.2.9 and from 4.3.0 up to but not including 4.3.3. The issue arises because the OAuth2 token expiry validation incorrectly skips checks when the token's 'exp' claim is a floating-point number rather than an integer. This allows an attacker with a previously valid signed token containing a float 'exp' value to bypass expiry checks, causing the server to accept expired tokens and maintain connections indefinitely. The vulnerability is fixed in versions 4.2.9 and 4.3.3.

Impact

An attacker possessing a previously valid signed OAuth2 token with a floating-point 'exp' claim can bypass token expiry checks, allowing the use of expired tokens to maintain unauthorized connections indefinitely. This undermines session expiration controls and could lead to unauthorized access persistence. The vulnerability does not require user interaction and can be exploited remotely.

Summary

RabbitMQ's OAuth2 token expiry validation functions validatetokenexpiry/1 and expirytimestamp/1 only check token expiry if the 'exp' claim is an integer, ignoring floating-point values. Since RFC 7519 permits fractional NumericDate, tokens with float 'exp' values bypass expiry validation. The josejwt:verify function validates only the signature and not the expiry. Consequently, if an Identity Provider (IdP) emits an 'exp' as a float, both login-time expiry checks and mid-connection disconnect timers are skipped, allowing expired tokens to be accepted and connections to persist indefinitely. This flaw affects rabbitmq-server versions >=4.2.0 <4.2.9 and >=4.3.0 <4.3.3 and is resolved in versions 4.2.9 and 4.3.3.

CWE-613DEPRECATED: Insufficient Session Expiration (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
This entry has been deprecated because it was insufficiently clear. Consider CWE-1462 and its descendants.
MITRE does not allow mapping vulnerabilities to this entry; it groups weaknesses rather than naming one.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.1 (opens in a new tab)
V2.8.6 (opens in a new tab)
V3.6.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Oct 2026, 17:05 UTC

WeaknessesCWE-613

Technical details

References

Community reviews

Related threats