CVE-2026-77903

CRITICALPre-NVD 9.09.0—
EchelonGraph scoreHIGH confidence

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-18. a secondary CVSS source baseline 9.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.0Exploit: None knownExposed: 0

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

Authentication bypass by spoofing in Microsoft Dataverse allows an unauthorized attacker to elevate privileges over a network.

CVSS v3
9.0
EG Score
9.0(high)
EG Risk
41(Track)
EG Risk 41/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
Severity90% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 19, 2026

Advisory Details (1)

Auto-updated Sep 17, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-77903

Vendor Advisories for CVE-2026-77903(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.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 44× in last 7d / 44× 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-19 21:56 UTCVendor advisory
  2. 2026-09-19 21:56 UTCGHSA enrichment
  3. 2026-09-19 17:35 UTCEG score recompute
  4. 2026-09-19 17:35 UTCVendor advisory
  5. 2026-09-19 17:35 UTCGHSA enrichment
  6. 2026-09-19 13:14 UTCVendor advisory
  7. 2026-09-19 13:14 UTCGHSA enrichment
  8. 2026-09-19 08:52 UTCVendor advisory
  9. 2026-09-19 08:52 UTCGHSA enrichment
  10. 2026-09-19 04:31 UTCEG score recompute
  11. 2026-09-19 04:31 UTCVendor advisory
  12. 2026-09-19 04:31 UTCGHSA enrichment
  13. 2026-09-19 04:01 UTCVendor advisory
  14. 2026-09-19 04:01 UTCGHSA enrichment
  15. 2026-09-19 01:06 UTCVendor advisory
  16. 2026-09-19 01:06 UTCGHSA enrichment
  17. 2026-09-18 20:46 UTCEG score recompute
  18. 2026-09-18 20:46 UTCVendor advisory
  19. 2026-09-18 20:46 UTCGHSA enrichment
  20. 2026-09-18 19:44 UTCEG score recompute
  21. 2026-09-18 19:44 UTCVendor advisory
  22. 2026-09-18 19:44 UTCGHSA enrichment
  23. 2026-09-18 19:28 UTCEPSS rescore
  24. 2026-09-18 15:23 UTCEG score recompute
  25. 2026-09-18 15:23 UTCVendor advisory
Show 19 more
  1. 2026-09-18 15:23 UTCGHSA enrichment
  2. 2026-09-18 14:35 UTCEG score recompute
  3. 2026-09-18 14:35 UTCVendor advisory
  4. 2026-09-18 14:35 UTCGHSA enrichment
  5. 2026-09-18 13:50 UTCEG score recompute
  6. 2026-09-18 13:50 UTCVendor advisory
  7. 2026-09-18 13:50 UTCGHSA enrichment
  8. 2026-09-18 12:29 UTCVendor advisory
  9. 2026-09-18 12:29 UTCGHSA enrichment
  10. 2026-09-18 08:07 UTCVendor advisory
  11. 2026-09-18 08:07 UTCGHSA enrichment
  12. 2026-09-18 03:46 UTCEG score recompute
  13. 2026-09-18 03:46 UTCVendor advisory
  14. 2026-09-18 03:46 UTCGHSA enrichment
  15. 2026-09-17 23:25 UTCEG score recompute
  16. 2026-09-17 23:25 UTCVendor advisory
  17. 2026-09-17 23:05 UTCEG score recompute
  18. 2026-09-17 23:05 UTCVendor advisory
  19. 2026-09-17 23:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-77903?
CVE-2026-77903 is a critical vulnerability published on September 17, 2026. Authentication bypass by spoofing in Microsoft Dataverse allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-77903 disclosed?
CVE-2026-77903 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77903 actively exploited?
CVE-2026-77903 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 68.1% of all scored CVEs.
What is the CVSS score of CVE-2026-77903?
CVE-2026-77903 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-77903?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77903, 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-77903

Explore →

Is Your Infrastructure Affected by CVE-2026-77903?

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

Start Free Scan →Browse All CVEs