CVE-2026-42899

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 2.4%, top 17% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Loop with unreachable exit condition ('infinite loop') in ASP.NET Core allows an unauthorized attacker to deny service over a network.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
50
EG Risk 50/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
Severity75% × 45%
Exploitation2% × 40%
Automatability100% × 15%
EPSS PROB
2.4%
EPSS %ILE
83rd
KEV
Not listed

Published

May 12, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated May 13, 2026
Patch available. 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-42899

Vendor Advisories for CVE-2026-42899(18)

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntunetstandard-targeting-pack-2.1-8.0 (8.0.127-0ubuntu1~24.04.1) @ noble2026-08-23ubuntu
redhatdotnet8.0-0:8.0.127-1.el9_62026-06-08redhat
redhatdotnet9.0-0:9.0.117-1.el10_02026-06-08redhat
redhatdotnet8.0-0:8.0.127-1.el9_42026-06-08redhat
redhatdotnet8.0-0:8.0.127-1.el10_02026-06-08redhat
redhatdotnet9.0-0:9.0.117-1.el9_62026-06-08redhat
redhatdotnet10.0-0:10.0.108-1.el10_22026-06-01redhat
redhatdotnet9.0-0:9.0.117-1.el10_22026-05-28redhat
redhatdotnet9.0-0:9.0.117-1.el8_102026-05-27redhat
redhatdotnet10.0-0:10.0.108-1.el9_82026-05-27redhat
redhatdotnet10.0-0:10.0.108-1.el8_102026-05-27redhat
redhatdotnet9.0-0:9.0.117-1.el9_82026-05-27redhat
redhatdotnet8.0-0:8.0.127-1.el10_22026-05-27redhat
redhatdotnet8.0-0:8.0.127-1.el8_102026-05-27redhat
redhatdotnet8.0-0:8.0.127-1.el9_82026-05-27redhat
redhatdotnet10-0-main-10.0.108-1.hum12026-05-14redhat
redhatdotnet9-0-main-9.0.117-1.hum12026-05-14redhat
redhatdotnet8-0-main-8.0.127-1.hum12026-05-14redhat

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

(12 across 1 ecosystem)
NuGet(12)
PackageVulnerable rangeFix by version rangeDependents
Microsoft.AspNetCore.App.Runtime.linux-arm10.0.0 ... 10.0.7 (8 versions)
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
—
Microsoft.AspNetCore.App.Runtime.linux-arm6410.0.0 ... 10.0.7 (8 versions)
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
—
Microsoft.AspNetCore.App.Runtime.linux-musl-arm10.0.0 ... 10.0.7 (8 versions)
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
—
Microsoft.AspNetCore.App.Runtime.linux-musl-arm6410.0.0 ... 10.0.7 (8 versions)
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
—
Microsoft.AspNetCore.App.Runtime.linux-musl-x649.0.0 ... 9.0.9 (16 versions)
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
—
Microsoft.AspNetCore.App.Runtime.linux-x6410.0.0 ... 10.0.7 (8 versions)
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
—
Microsoft.AspNetCore.App.Runtime.osx-arm6410.0.0 ... 10.0.7 (8 versions)
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
—
Microsoft.AspNetCore.App.Runtime.osx-x6410.0.0 ... 10.0.7 (8 versions)
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
—
Microsoft.AspNetCore.App.Runtime.win-arm—
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
—
Microsoft.AspNetCore.App.Runtime.win-arm6410.0.0 ... 10.0.7 (8 versions)
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
—
Microsoft.AspNetCore.App.Runtime.win-x6410.0.0 ... 10.0.7 (8 versions)
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
—
Microsoft.AspNetCore.App.Runtime.win-x8610.0.0 ... 10.0.7 (8 versions)
  • 8.0.0 up to 8.0.27: fixed in 8.0.27
  • 9.0.0 up to 9.0.16: fixed in 9.0.16
  • 10.0.0 up to 10.0.8: fixed in 10.0.8
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 7× in last 7d / 21× 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 221 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

5 shown

redhat:RHSA-2026:21286 · redhat:RHSA-2026:17527 · redhat:RHSA-2026:17682

Frequently asked(5)

What is CVE-2026-42899?
CVE-2026-42899 is a high vulnerability published on May 12, 2026. Loop with unreachable exit condition ('infinite loop') in ASP.NET Core allows an unauthorized attacker to deny service over a network.
When was CVE-2026-42899 disclosed?
CVE-2026-42899 was first published on May 12, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42899 actively exploited?
CVE-2026-42899 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% probability of exploitation in the next 30 days (83rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42899?
CVE-2026-42899 has a CVSS base score of 7.5 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-42899?
A fix for CVE-2026-42899 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42899 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-42899?

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

Book a Demo →Browse All CVEs