CVE-2026-62874

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
10.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: 10.0Exploit: None knownExposed: 0

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

Insufficient verification of data authenticity in Azure Billing allows an unauthorized attacker to elevate privileges over a network.

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

Published

September 17, 2026

Last Modified

September 19, 2026

Advisory Details (1)

Auto-updated Sep 19, 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-62874

Vendor Advisories for CVE-2026-62874(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 42× in last 7d / 42× 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 20:48 UTCVendor advisory
  2. 2026-09-19 20:48 UTCGHSA enrichment
  3. 2026-09-19 16:44 UTCEG score recompute
  4. 2026-09-19 16:44 UTCVendor advisory
  5. 2026-09-19 16:44 UTCGHSA enrichment
  6. 2026-09-19 12:41 UTCVendor advisory
  7. 2026-09-19 12:40 UTCGHSA enrichment
  8. 2026-09-19 08:35 UTCVendor advisory
  9. 2026-09-19 08:35 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 00:58 UTCVendor advisory
  16. 2026-09-19 00:57 UTCGHSA enrichment
  17. 2026-09-18 20:54 UTCEG score recompute
  18. 2026-09-18 20:54 UTCVendor advisory
  19. 2026-09-18 20:54 UTCGHSA enrichment
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-18 18:08 UTCVendor advisory
  22. 2026-09-18 18:08 UTCGHSA enrichment
  23. 2026-09-18 14:00 UTCVendor advisory
  24. 2026-09-18 14:00 UTCGHSA enrichment
  25. 2026-09-18 13:22 UTCEG score recompute
Show 17 more
  1. 2026-09-18 13:22 UTCVendor advisory
  2. 2026-09-18 13:22 UTCGHSA enrichment
  3. 2026-09-18 13:14 UTCEG score recompute
  4. 2026-09-18 13:14 UTCVendor advisory
  5. 2026-09-18 13:14 UTCGHSA enrichment
  6. 2026-09-18 12:39 UTCVendor advisory
  7. 2026-09-18 12:39 UTCGHSA enrichment
  8. 2026-09-18 08:35 UTCVendor advisory
  9. 2026-09-18 08:35 UTCGHSA enrichment
  10. 2026-09-18 04:32 UTCEG score recompute
  11. 2026-09-18 04:32 UTCVendor advisory
  12. 2026-09-18 04:32 UTCGHSA enrichment
  13. 2026-09-18 00:28 UTCEG score recompute
  14. 2026-09-18 00:28 UTCVendor advisory
  15. 2026-09-17 23:20 UTCEG score recompute
  16. 2026-09-17 23:20 UTCVendor advisory
  17. 2026-09-17 23:19 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-62874?
CVE-2026-62874 is a critical vulnerability published on September 17, 2026. Insufficient verification of data authenticity in Azure Billing allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-62874 disclosed?
CVE-2026-62874 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-62874 actively exploited?
CVE-2026-62874 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 75.3% of all scored CVEs.
What is the CVSS score of CVE-2026-62874?
CVE-2026-62874 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-62874?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62874, 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-62874

Explore →

Is Your Infrastructure Affected by CVE-2026-62874?

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

Start Free Scan →Browse All CVEs