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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-613"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67242.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.9"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"introduced": "4.3.0"
},
{
"fixed": "4.3.3"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "d10a369a96658d0fba1050bd43c732e58fcf28fd"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "f189a8824c9efbce46bd9438fcdbda4521cfc923"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "v4.2.9",
"range": [
{
"fixed": "47d6d6457c7d1a440daed643cb7d76bba313e79c"
}
],
"source": "REFERENCES_TAG"
},
{
"original_tag": "v4.3.3",
"range": [
{
"fixed": "1d284b2d2a1e2f845ad22b0d5ee38ec372d50802"
}
],
"source": "REFERENCES_TAG"
}
]
}