CVE-2026-67242 Vulnerability Analysis & Exploit Details

CVE-2026-67242
Vulnerability Scoring

5.4
/10
Significant Risk

Security assessments indicate that CVE-2026-67242 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-67242 Details

Status: Analyzed

Last updated: 🕓 16 Oct 2026, 16:22 UTC
Originally published on: 🕔 25 Sep 2026, 17:17 UTC

Time between publication and last update: 20 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

CVE-2026-67242 Vulnerability Summary

CVE-2026-67242: 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.

Assessing the Risk of CVE-2026-67242

Access Complexity Graph

The exploitability of CVE-2026-67242 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-67242

CVE-2026-67242 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-67242, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-67242, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2026-67242 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2026-67242 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2026-67242 does not impact system availability.

CVE-2026-67242 References

External References

CWE Common Weakness Enumeration

CWE-613

Vulnerable Configurations

  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta3:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta3:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta4:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.0:beta4:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:-:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:rc0:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:rc0:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:broadcom:rabbitmq_server:4.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:broadcom:rabbitmq_server:4.3.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-67242: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-110879 – jackson-databind validates the outer class of a class-name type ID but accepts attacker-selected classes inside its generic arguments, even when th...
  • CVE-2026-110747 – ProtobufParser._readStringKey() reads the length prefix of a protobuf map entry's string key into an attacker-controlled int and then checks (_inpu...
  • CVE-2026-118129 – A vulnerability was found in jeremyckahn Chitchatter up to f82538633813c854a81a8b2112a2f6ba17b39cbc. The affected element is the function isConfigM...
  • CVE-2026-104895 – The asynchronous Smile parser (NonBlockingByteArrayParser) uses a raw-binary length prefix taken from untrusted input to allocate a byte[] before t...
  • CVE-2026-104016 – ProtobufParser parses length-prefixed protobuf string and bytes fields by checking (_inputPtr + len) <= _inputEnd and then, on the fast path, calli...