CVE-2026-80209

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.3 from GitHub Security Advisory published 2026-08-27. The CNA's CVSS baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists fonoster versions up to and including 0.22.7 as affected. No release containing a fix is confirmed on record.

The updateWorkspace handler in mods/identity/src/workspaces/createUpdateWorkspace.ts in Fonoster through 0.22.7 invokes the gRPC callback with PERMISSION_DENIED when createIsWorkspaceMember reports that the caller is not a member of the target workspace, but it does not return. Execution continues into prisma.workspace.update, which is scoped by the workspace reference alone, so the rename commits before the second callback is issued and the caller receives a permission error for a write that already succeeded. The gRPC interceptor in mods/common/src/identity/createAuthInterceptor.ts binds the workspace accessKeyId to the caller's token only for paths in workspaceResourceAccess or workspaceResourceOwnerOrAdminAccess, and Identity/UpdateWorkspace is listed in fullIdentityAccess, which the base USER role holds. Any authenticated user can therefore rename an arbitrary workspace in the deployment.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity43% × 45%
The EG Score, 4.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Aug 27, 2026
No fix on record yet.
Web page

Fonoster through 0.22.7 Incorrect Authorization in the Identity UpdateWorkspace Handler | Advisories | VulnCheck

https://www.vulncheck.com/advisories/fonoster-through-0.22.7-incorrect-authorization-in-the-identity-updateworkspace-handler
Web page

fonoster/mods/identity/src/workspaces/createUpdateWorkspace.ts at v0.22.7 · fonoster/fonoster · GitHub

https://github.com/fonoster/fonoster/blob/v0.22.7/mods/identity/src/workspaces/createUpdateWorkspace.ts#L47
Web page

GitHub - fonoster/fonoster: 🚀 The open-source alternative to Twilio. · GitHub

https://github.com/fonoster/fonoster
Web page

Cross-workspace authorization bypass in Identity/UpdateWorkspace · Issue #861 · fonoster/fonoster · GitHub

https://github.com/fonoster/fonoster/issues/861

Vendor Advisories for CVE-2026-80209(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 137 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 39 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-10-12 14:57 UTCEG score recompute
  4. 2026-10-11 19:21 UTCEG score recompute
  5. 2026-10-11 16:37 UTCEG score recompute
  6. 2026-10-11 13:56 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-10 01:56 UTCEG score recompute
  10. 2026-10-10 01:56 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-09 03:08 UTCEG score recompute
  13. 2026-10-09 03:07 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-08 01:21 UTCEG score recompute
  16. 2026-10-08 01:20 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-06 22:52 UTCEG score recompute
  19. 2026-10-06 22:52 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-06 00:54 UTCEG score recompute
  22. 2026-10-06 00:54 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  23. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-10-05 01:27 UTCEG score recompute
  25. 2026-10-05 01:27 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
Show 73 more
  1. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-10-04 03:29 UTCEG score recompute
  3. 2026-10-04 03:29 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  4. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-10-03 05:30 UTCEG score recompute
  6. 2026-10-03 05:30 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  7. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-02 07:31 UTCEG score recompute
  9. 2026-10-02 07:31 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  10. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-01 09:32 UTCEG score recompute
  12. 2026-10-01 09:32 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  13. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-09-30 11:34 UTCEG score recompute
  15. 2026-09-30 11:34 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  16. 2026-09-29 12:39 UTCEG score recompute
  17. 2026-09-29 12:39 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  18. 2026-09-28 14:41 UTCEG score recompute
  19. 2026-09-28 14:41 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  20. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-09-27 16:43 UTCEG score recompute
  22. 2026-09-27 16:43 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-09-26 18:45 UTCEG score recompute
  25. 2026-09-26 18:45 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  26. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  27. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  28. 2026-09-25 13:01 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  29. 2026-09-24 14:58 UTCEG score recompute
  30. 2026-09-24 14:58 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  31. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  32. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  33. 2026-09-23 17:25 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  34. 2026-09-22 19:58 UTCEG score recompute
  35. 2026-09-22 19:58 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  36. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  37. 2026-09-21 21:59 UTCEG score recompute
  38. 2026-09-21 21:59 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  39. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  40. 2026-09-21 00:01 UTCEG score recompute
  41. 2026-09-21 00:01 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  42. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  43. 2026-09-20 02:02 UTCEG score recompute
  44. 2026-09-20 02:02 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  45. 2026-09-19 04:03 UTCEG score recompute
  46. 2026-09-19 04:03 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  47. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-09-18 06:05 UTCEG score recompute
  49. 2026-09-18 06:05 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  50. 2026-09-17 08:06 UTCEG score recompute
  51. 2026-09-17 08:06 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  52. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  53. 2026-09-16 10:05 UTCEG score recompute
  54. 2026-09-16 10:05 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  55. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  56. 2026-09-15 12:06 UTCEG score recompute
  57. 2026-09-15 12:06 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  58. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  59. 2026-09-14 14:07 UTCEG score recompute
  60. 2026-09-14 14:07 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  61. 2026-09-13 16:09 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  62. 2026-09-12 18:10 UTCEG score recompute
  63. 2026-09-12 18:10 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  64. 2026-09-11 20:12 UTCEG score recompute
  65. 2026-09-11 20:12 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  66. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  67. 2026-09-10 21:58 UTCEG score recompute
  68. 2026-09-10 21:58 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  69. 2026-09-10 00:00 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  70. 2026-09-09 00:41 UTCEG score recompute
  71. 2026-09-09 00:41 UTCGHSA enrichmentGHSA-xqrc-3jm3-hm6q · GitHub CVSS 4.3
  72. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  73. 2026-09-07 20:32 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-80209?
CVE-2026-80209 is a medium-severity vulnerability; its CVE record was published on August 27, 2026. The updateWorkspace handler in mods/identity/src/workspaces/createUpdateWorkspace.ts in Fonoster through 0.22.7 invokes the gRPC callback with PERMISSION_DENIED when createIsWorkspaceMember reports that the caller is not a member of the target workspace, but it does not return. Execution continues…
When was CVE-2026-80209 made public?
CVE-2026-80209 was made public on July 1, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-80209 actively exploited?
CVE-2026-80209 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80209?
CVE-2026-80209 has a CVSS base score of 4.3 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-80209?
No fix for CVE-2026-80209 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists fonoster versions up to and including 0.22.7 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-80209 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-80209?

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

Book a Demo →Browse All CVEs