CVE-2026-54238 (GCVE-0-2026-54238)
Vulnerability from cvelistv5
Published
2026-10-22 17:22
Modified
2026-10-30 15:11
Severity ?
VLAI Severity ?
EPSS score ?
CWE
- CWE-613 - Insufficient Session Expiration
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.
References
| URL | Tags | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-54238",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-30T15:11:24.865400Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-30T15:11:34.608Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"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-30T15:11:34.608Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-54238\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-10-30T15:11:24.865400Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-10-30T15:11:29.226Z\"}}], \"cna\": {\"title\": \"Supabase Realtime: Expired JWTs with string exp are accepted by REST broadcast authorization\", \"source\": {\"advisory\": \"GHSA-hg9h-6mhq-6c2v\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 3.1, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"LOW\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N\", \"integrityImpact\": \"LOW\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"HIGH\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"NONE\"}}], \"affected\": [{\"vendor\": \"supabase\", \"product\": \"realtime\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003c 2.103.1\"}]}], \"references\": [{\"url\": \"https://github.com/supabase/realtime/security/advisories/GHSA-hg9h-6mhq-6c2v\", \"name\": \"https://github.com/supabase/realtime/security/advisories/GHSA-hg9h-6mhq-6c2v\", \"tags\": [\"x_refsource_CONFIRM\"]}, {\"url\": \"https://github.com/supabase/realtime/pull/1934\", \"name\": \"https://github.com/supabase/realtime/pull/1934\", \"tags\": [\"x_refsource_MISC\"]}, {\"url\": \"https://github.com/supabase/realtime/commit/ac229d7eff2798b12b994e07bdd64f5e9b56374a\", \"name\": \"https://github.com/supabase/realtime/commit/ac229d7eff2798b12b994e07bdd64f5e9b56374a\", \"tags\": [\"x_refsource_MISC\"]}, {\"url\": \"https://github.com/supabase/realtime/releases/tag/v2.103.1\", \"name\": \"https://github.com/supabase/realtime/releases/tag/v2.103.1\", \"tags\": [\"x_refsource_MISC\"]}], \"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.\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-613\", \"description\": \"CWE-613: Insufficient Session Expiration\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2026-10-22T17:22:50.862Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2026-54238\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-10-30T15:11:34.608Z\", \"dateReserved\": \"2026-06-12T16:25:43.084Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2026-10-22T17:22:50.862Z\", \"assignerShortName\": \"GitHub_M\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…