CVE-2026-47300

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% 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: cna:microsoft, epss
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

Incorrect implementation of authentication algorithm in ASP.NET Core allows an authorized attacker to elevate privileges over a network.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 26, 2026

Advisory Details (1)

Auto-updated Jul 14, 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-47300

Vendor Advisories for CVE-2026-47300(14)

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

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntudotnet10 (10.0.110-10.0.10-0ubuntu1~26.04.1) @ resolute2026-07-27ubuntu
redhatdotnet8-0-main-8.0.129-2.1.hum12026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el10_22026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el10_22026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el8_102026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el9_82026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el9_82026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el8_102026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el9_82026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el10_22026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el8_102026-07-20redhat
redhatdotnet9-0-main-9.0.119-1.hum12026-07-15redhat
redhatdotnet10-0-main-10.0.109-1.hum12026-06-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
Microsoft.AspNetCore.Authentication.Negotiate8.0.0 ... 8.0.8 (28 versions)8.0.29—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 14× in last 7d / 30× 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-07-27 05:53 UTCVendor advisory
  2. 2026-07-26 17:21 UTCVendor advisory
  3. 2026-07-26 17:13 UTCEG score recompute
  4. 2026-07-26 17:13 UTCVendor advisory
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 04:40 UTCEG score recompute
  7. 2026-07-26 04:40 UTCVendor advisory
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-24 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:17 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 02:41 UTCEG score recompute
  17. 2026-07-19 02:41 UTCVendor advisory
  18. 2026-07-19 02:29 UTCEPSS rescore
  19. 2026-07-18 10:04 UTCEPSS rescore
  20. 2026-07-17 07:17 UTCEG score recompute
  21. 2026-07-17 07:17 UTCVendor advisory
  22. 2026-07-16 20:42 UTCVendor advisory
  23. 2026-07-16 17:03 UTCEPSS rescore
  24. 2026-07-16 08:10 UTCVendor advisory
  25. 2026-07-15 19:38 UTCVendor advisory
Show 5 more
  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 07:07 UTCVendor advisory
  3. 2026-07-14 18:35 UTCEG score recompute
  4. 2026-07-14 18:35 UTCVendor advisory
  5. 2026-07-14 18:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-47300?
CVE-2026-47300 is a high vulnerability published on July 14, 2026. Incorrect implementation of authentication algorithm in ASP.NET Core allows an authorized attacker to elevate privileges over a network.
When was CVE-2026-47300 disclosed?
CVE-2026-47300 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47300 actively exploited?
CVE-2026-47300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.5% of all scored CVEs.
What is the CVSS score of CVE-2026-47300?
CVE-2026-47300 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-47300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47300, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47300

Explore →

Is Your Infrastructure Affected by CVE-2026-47300?

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

Start Free Scan →Browse All CVEs