CVE-2026-54238 (GCVE-0-2026-54238)
Vulnerability from cvelistv5 – Published: 2026-10-22 17:22 – Updated: 2026-10-22 17:22
VLAI
EPSS
VEX
Title
Supabase Realtime: Expired JWTs with string exp are accepted by REST broadcast authorization
Summary
Supabase Realtime provides Broadcast, Presence, and Postgres Changes via WebSockets. Prior to version 2.103.1, the REST broadcast endpoints accept an expired JWT when the exp claim is encoded as a JSON string instead of a JSON number. The same route rejects an expired integer exp token signed with the same tenant secret. The accepted request returns 202 and emits the broadcast to subscribers. This could allow an unauthenticated attacker can broadcast realtime messages to subscribers. The attack can be performed via the Internet/only from within the supabase project. The impact of broadcasting messages to subscribers is application specific. This issue has been patched in version 2.103.1.
Severity
CWE
- CWE-613 - Insufficient Session Expiration
Assigner
References
4 references
| URL | Tags |
|---|---|
| https://github.com/supabase/realtime/security/adv… | x_refsource_CONFIRM |
| https://github.com/supabase/realtime/pull/1934 | x_refsource_MISC |
| https://github.com/supabase/realtime/commit/ac229… | x_refsource_MISC |
| https://github.com/supabase/realtime/releases/tag… | x_refsource_MISC |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"product": "realtime",
"vendor": "supabase",
"versions": [
{
"status": "affected",
"version": "\u003c 2.103.1"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Supabase Realtime provides Broadcast, Presence, and Postgres Changes via WebSockets. Prior to version 2.103.1, the REST broadcast endpoints accept an expired JWT when the exp claim is encoded as a JSON string instead of a JSON number. The same route rejects an expired integer exp token signed with the same tenant secret. The accepted request returns 202 and emits the broadcast to subscribers. This could allow an unauthenticated attacker can broadcast realtime messages to subscribers. The attack can be performed via the Internet/only from within the supabase project. The impact of broadcasting messages to subscribers is application specific. This issue has been patched in version 2.103.1."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 3.1,
"baseSeverity": "LOW",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-613",
"description": "CWE-613: Insufficient Session Expiration",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-22T17:22:50.862Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/supabase/realtime/security/advisories/GHSA-hg9h-6mhq-6c2v",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/supabase/realtime/security/advisories/GHSA-hg9h-6mhq-6c2v"
},
{
"name": "https://github.com/supabase/realtime/pull/1934",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/supabase/realtime/pull/1934"
},
{
"name": "https://github.com/supabase/realtime/commit/ac229d7eff2798b12b994e07bdd64f5e9b56374a",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/supabase/realtime/commit/ac229d7eff2798b12b994e07bdd64f5e9b56374a"
},
{
"name": "https://github.com/supabase/realtime/releases/tag/v2.103.1",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/supabase/realtime/releases/tag/v2.103.1"
}
],
"source": {
"advisory": "GHSA-hg9h-6mhq-6c2v",
"discovery": "UNKNOWN"
},
"title": "Supabase Realtime: Expired JWTs with string exp are accepted by REST broadcast authorization"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-54238",
"datePublished": "2026-10-22T17:22:50.862Z",
"dateReserved": "2026-06-12T16:25:43.084Z",
"dateUpdated": "2026-10-22T17:22:50.862Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-54238",
"date": "2026-10-27",
"epss": "0.00206",
"percentile": "0.10655"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"product": "realtime",
"vendor": "supabase",
"versions": [
{
"status": "affected",
"version": "\u003c 2.103.1"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Supabase Realtime provides Broadcast, Presence, and Postgres Changes via WebSockets. Prior to version 2.103.1, the REST broadcast endpoints accept an expired JWT when the exp claim is encoded as a JSON string instead of a JSON number. The same route rejects an expired integer exp token signed with the same tenant secret. The accepted request returns 202 and emits the broadcast to subscribers. This could allow an unauthenticated attacker can broadcast realtime messages to subscribers. The attack can be performed via the Internet/only from within the supabase project. The impact of broadcasting messages to subscribers is application specific. This issue has been patched in version 2.103.1."
}
],
"id": "CVE-2026-54238",
"lastModified": "2026-10-23T19:42:24.553",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 3.1,
"baseSeverity": "LOW",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.6,
"impactScore": 1.4,
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
},
"published": "2026-10-22T18:17:28.993",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/supabase/realtime/commit/ac229d7eff2798b12b994e07bdd64f5e9b56374a"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/supabase/realtime/pull/1934"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/supabase/realtime/releases/tag/v2.103.1"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/supabase/realtime/security/advisories/GHSA-hg9h-6mhq-6c2v"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Awaiting Analysis",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-613"
}
],
"source": "security-advisories@github.com",
"type": "Primary"
}
]
}
}
}
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.