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 58% 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 — Patch released 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
42%
KEV
Not listed

Published

July 14, 2026

Last Modified

August 28, 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(19)

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

Patch Availability(18)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunetstandard-targeting-pack-2.1-8.0 (8.0.129-0ubuntu1~24.04.1) @ noble2026-08-30ubuntu
redhatdotnet9.0-0:9.0.120-1.el9_62026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el10_02026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_42026-08-24redhat
redhatdotnet8.0-0:8.0.130-1.el9_62026-08-24redhat
redhatdotnet9.0-0:9.0.120-1.el10_02026-08-24redhat
redhatdotnet8-0-main-8.0.129-2.1.hum12026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el8_102026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el9_82026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el9_82026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el9_82026-07-20redhat
redhatdotnet8.0-0:8.0.129-1.el10_22026-07-20redhat
redhatdotnet10.0-0:10.0.110-1.el10_22026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el10_22026-07-20redhat
redhatdotnet9.0-0:9.0.119-1.el8_102026-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 20× in last 7d / 114× 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.

Showing the most recent 100 of 163 total refreshes for this CVE.

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

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 August 28, 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 57.6% 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