CVE-2026-83947

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-10-09. A secondary CVSS source baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.7EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.7Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Missing authorization in Azure Event Grid allows an authorized attacker to perform spoofing over a network.

CVSS v3
7.7
EG Score
7.7HIGHhigh 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)
Severity77% × 45%
The EG Score, 7.7 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (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

October 8, 2026

Last Modified

October 9, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
Fix referenced — no release confirmed yet. Sources: microsoft.
microsoftMentions a patch (unverified)

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-83947

Vendor Advisories for CVE-2026-83947(2)

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 30× in last 7d / 30× 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.

  1. 2026-10-11 18:37 UTCVendor advisory
  2. 2026-10-11 18:37 UTCGHSA enrichmentGHSA-hf67-p98c-9g49 · GitHub severity HIGH · GitHub CVSS 7.7
  3. 2026-10-11 16:35 UTCEG score recompute
  4. 2026-10-11 13:53 UTCEG score recompute
  5. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-10-11 06:13 UTCEG score recompute
  7. 2026-10-11 06:13 UTCVendor advisory
  8. 2026-10-11 06:13 UTCGHSA enrichmentGHSA-hf67-p98c-9g49 · GitHub severity HIGH · GitHub CVSS 7.7
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-10 17:49 UTCGHSA enrichmentGHSA-hf67-p98c-9g49 · GitHub severity HIGH · GitHub CVSS 7.7
  11. 2026-10-10 05:25 UTCEG score recompute
  12. 2026-10-10 05:25 UTCVendor advisory
  13. 2026-10-10 05:25 UTCGHSA enrichmentGHSA-hf67-p98c-9g49 · GitHub severity HIGH · GitHub CVSS 7.7
  14. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-09 17:01 UTCVendor advisory
  16. 2026-10-09 17:01 UTCGHSA enrichmentGHSA-hf67-p98c-9g49 · GitHub severity HIGH · GitHub CVSS 7.7
  17. 2026-10-09 15:33 UTCEG score recompute
  18. 2026-10-09 15:33 UTCVendor advisory
  19. 2026-10-09 15:33 UTCGHSA enrichmentGHSA-hf67-p98c-9g49 · GitHub severity HIGH · GitHub CVSS 7.7
  20. 2026-10-09 14:59 UTCEG score recompute
  21. 2026-10-09 14:59 UTCVendor advisory
  22. 2026-10-09 14:59 UTCGHSA enrichmentGHSA-hf67-p98c-9g49 · GitHub severity HIGH · GitHub CVSS 7.7
  23. 2026-10-09 11:47 UTCEG score recompute
  24. 2026-10-09 11:47 UTCVendor advisory
  25. 2026-10-09 11:46 UTCGHSA enrichmentGHSA-hf67-p98c-9g49 · GitHub severity HIGH · GitHub CVSS 7.7
Show 5 more
  1. 2026-10-08 23:22 UTCEG score recompute
  2. 2026-10-08 23:22 UTCVendor advisory
  3. 2026-10-08 22:29 UTCEG score recompute
  4. 2026-10-08 22:29 UTCVendor advisory
  5. 2026-10-08 22:28 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-83947?
CVE-2026-83947 is a high-severity vulnerability; its CVE record was published on October 8, 2026. Missing authorization in Azure Event Grid allows an authorized attacker to perform spoofing over a network.
When was CVE-2026-83947 made public?
CVE-2026-83947 was made public on October 8, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on October 8, 2026. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-83947 actively exploited?
CVE-2026-83947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-83947?
CVE-2026-83947 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-83947?
A fix for CVE-2026-83947 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-83947 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-83947?

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

Book a Demo →Browse All CVEs