Is CVE-2026-67242 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-67242 being exploited in the wild.

How severe is CVE-2026-67242?

Informational severity, published 25 September 2026.

Which products and versions are affected?

VMware RabbitMQ 4.2.0 to 4.2.8, 4.3.0 to 4.3.2.

Is there a fix for CVE-2026-67242?

A patch was published on 2026-09-25: Fixed in versions 4.2.9 and 4.3.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67242 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-67242?

Check whether you run VMware RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-67242: RabbitMQ OAuth2 token expiry bypass for fractional exp

CVE-2026-67242 · Severity: info · Published 2026-09-25

RabbitMQ is a message broker that organizations use to route and queue data between applications. When using OAuth2 authentication with an identity provider that emits expiry timestamps as decimal numbers (which the OAuth2 standard permits), RabbitMQ fails to validate whether tokens have expired. An attacker with a previously-valid token could maintain unauthorized access to the message broker even after the token's intended expiry time.

Technologies: VMware RabbitMQ. Vendors: VMware.

Quick answers

Is CVE-2026-67242 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67242 being exploited in the wild.
How severe is CVE-2026-67242?: Informational severity, published 25 September 2026.
Which products and versions are affected?: VMware RabbitMQ 4.2.0 to 4.2.8, 4.3.0 to 4.3.2.
Is there a fix for CVE-2026-67242?: A patch was published on 2026-09-25: Fixed in versions 4.2.9 and 4.3.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67242 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67242?: Check whether you run VMware RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a logic error in token expiry validation in the OAuth2 backend. The validate_token_expiry/1 and expiry_timestamp/1 functions use guards checking is_integer(Exp), which causes them to fall through without validation when the identity provider emits exp (expiry) as a JSON float rather than integer, despite RFC 7519 permitting fractional NumericDate values. An attacker with a previously-valid signed token from an IdP that uses float exp timestamps can bypass both login-time and mid-connection disconnect timers.

Affected products

VMware RabbitMQ 4.2.0 to 4.2.8, 4.3.0 to 4.3.2

Timeline

2026-09-25: disclosed
2026-09-25: patched: Fixed in versions 4.2.9 and 4.3.3

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.