CVE-2026-62247

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Supabase Realtime provides Broadcast, Presence, and Postgres Changes via WebSockets. Prior to 2.111.2, Realtime authorization does not correctly honor the per-extension presence.read row-level security policy when a private-channel client is allowed presence.write but explicitly denied presence.read. Under that differential policy, the client can receive presence_diff messages containing other members' presence metadata, including application-defined location, online-status, roster, viewing, or typing information. Deployments with uniform presence visibility have no differential, and postgres_changes row data is unaffected. This issue is fixed in version 2.111.2.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

September 21, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Sep 21, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available

v2.111.2

Patch available: supabase/realtime v2.111.2

https://github.com/supabase/realtime/releases/tag/v2.111.2
github_commit Patch Available

commit c039bca9b57c (supabase/realtime)

Patch available: supabase/realtime v2.134.4 (contains commit c039bca9b57c)

https://github.com/supabase/realtime/commit/c039bca9b57c2e554a67fdf462970b54641d82eb
github_pr Patch Available

fix: ensure presence.read permission is respected

Patch available: supabase/realtime v2.134.4 (PR #1969 merged 2026-06-23)

https://github.com/supabase/realtime/pull/1969
github Patch Available

Incorrect Authorization in supabase/realtime · Advisory · supabase/realtime · GitHub

https://github.com/supabase/realtime/security/advisories/GHSA-rcr8-2525-4r7p

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 17:05 UTCEG score recompute
  2. 2026-09-23 17:54 UTCEPSS rescore
  3. 2026-09-22 16:22 UTCEG score recompute
  4. 2026-09-22 15:45 UTCEG score recompute
  5. 2026-09-21 20:18 UTCEG score recompute
  6. 2026-09-21 19:20 UTCEG score recompute
  7. 2026-09-21 19:20 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62247?
CVE-2026-62247 is a medium vulnerability published on September 21, 2026. Supabase Realtime provides Broadcast, Presence, and Postgres Changes via WebSockets. Prior to 2.111.2, Realtime authorization does not correctly honor the per-extension presence.read row-level security policy when a private-channel client is allowed presence.write but explicitly denied…
When was CVE-2026-62247 disclosed?
CVE-2026-62247 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62247 actively exploited?
CVE-2026-62247 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.5% of all scored CVEs.
What is the CVSS score of CVE-2026-62247?
CVE-2026-62247 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-62247?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62247, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62247

Explore →

Is Your Infrastructure Affected by CVE-2026-62247?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs