{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54238 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54238 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54238 is a low-severity vulnerability in supabase realtime, published on 22 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-54238 and fix it if it is affected.\n\nWhat it is: CVE-2026-54238 is a low-severity vulnerability in supabase realtime, published on 22 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-54238 in the wild and no public exploit code.\n\nAffected product: supabase realtime. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54238/ (Markdown: https://insights.sbomify.com/CVE-2026-54238/index.md)","id":"CVE-2026-54238","markdown":"https://insights.sbomify.com/CVE-2026-54238/index.md","name":"CVE-2026-54238","record":{"aliases":["GHSA-hg9h-6mhq-6c2v"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Supabase Realtime: Expired JWTs with string exp are accepted by REST broadcast authorization","id":"CVE-2026-54238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"FaustWP — Authentication Bypass via Initialization Vector Modification in Token Envelope","id":"CVE-2026-54239"},"packages":[],"prev":{"headline":"Wavelog: Unauthenticated Remote Code Execution","id":"CVE-2026-54237"},"products":["realtime"],"published":"2026-10-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-22","vendors":["supabase"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-54238/"}