rabbitmq-server — security advisory
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.
- Products
- rabbitmq-server
- Affected versions
- 4.0.5-10, 4.0.5-11, 4.0.5-12, 4.0.5-13, 4.0.5-14, 4.0.5-6, 4.0.5-8, 4.0.5-9, 4.3.0-1, 4.3.0-2, 4.3.0-3, 4.3.2-1, 4.3.2-2, 4.3.2-3, 4.3.2-4, 4.3.2-5
- Fixed versions
- 4.3.6-1
- CVEs
- CVE-2026-67242
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 01:48 UTC · Revision 1
Source evidence
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.
osv:DEBIAN-CVE-2026-67242
rabbitmq-server
Fixed versions: 4.3.6-1
Complete source record
{
"id": "fd81bafefa2589da3fbee5e5efa4065f950c4d618a4c754a1bc4b20e28421d9f",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2026-67242",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2026-67242",
"summary": "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.",
"evidence": "osv:DEBIAN-CVE-2026-67242",
"products": [
{
"name": {
"value": "rabbitmq-server",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.3.6-1",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": [
{
"value": "4.0.5-10",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-11",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-12",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-13",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-14",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-6",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-8",
"evidence": "/affected/0/versions"
},
{
"value": "4.0.5-9",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.0-1",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.0-2",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.0-3",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.2-1",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.2-2",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.2-3",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.2-4",
"evidence": "/affected/0/versions"
},
{
"value": "4.3.2-5",
"evidence": "/affected/0/versions"
}
]
}
],
"severity": "medium",
"structured": {
"id": "DEBIAN-CVE-2026-67242",
"aliases": [
"DEBIAN-CVE-2026-67242"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "4.3.6-1"
}
]
}
],
"package": {
"name": "rabbitmq-server",
"purl": "pkg:deb/debian/rabbitmq-server?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"versions": [
"4.0.5-10",
"4.0.5-11",
"4.0.5-12",
"4.0.5-13",
"4.0.5-14",
"4.0.5-6",
"4.0.5-8",
"4.0.5-9",
"4.3.0-1",
"4.3.0-2",
"4.3.0-3",
"4.3.2-1",
"4.3.2-2",
"4.3.2-3",
"4.3.2-4",
"4.3.2-5"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-67242.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-23T18:05:03.211617337Z",
"provider": "osv",
"upstream": [
"CVE-2026-67242"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2026-67242"
]
},
"related_cves": [
{
"value": "CVE-2026-67242",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 424250,
"published_at": "2026-09-25T17:17:12.337+00:00"
}