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: 1.2%, top 36% 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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 7.5Exploit: NoneExposed: 0

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.5(medium)
EG Risk
—
EPSS
82.5%
KEV
Not listed

Published

May 12, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated May 13, 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-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 / EcosystemFixed in / PatchReleasedSource
ubuntudotnet10 (10.0.108-10.0.8-0ubuntu1~26.04.1) @ resolute2026-06-28ubuntu
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 rangeFixed inDependents
Microsoft.AspNetCore.App.Runtime.linux-arm10.0.0 ... 10.0.7 (8 versions)10.0.8—
Microsoft.AspNetCore.App.Runtime.linux-arm6410.0.0 ... 10.0.7 (8 versions)10.0.8—
Microsoft.AspNetCore.App.Runtime.linux-musl-arm10.0.0 ... 10.0.7 (8 versions)10.0.8—
Microsoft.AspNetCore.App.Runtime.linux-musl-arm6410.0.0 ... 10.0.7 (8 versions)10.0.8—
Microsoft.AspNetCore.App.Runtime.linux-musl-x649.0.0 ... 9.0.9 (16 versions)9.0.16—
Microsoft.AspNetCore.App.Runtime.linux-x6410.0.0 ... 10.0.7 (8 versions)10.0.8—
Microsoft.AspNetCore.App.Runtime.osx-arm6410.0.0 ... 10.0.7 (8 versions)10.0.8—
Microsoft.AspNetCore.App.Runtime.osx-x6410.0.0 ... 10.0.7 (8 versions)10.0.8—
Microsoft.AspNetCore.App.Runtime.win-arm—10.0.8—
Microsoft.AspNetCore.App.Runtime.win-arm6410.0.0 ... 10.0.7 (8 versions)10.0.8—
Microsoft.AspNetCore.App.Runtime.win-x6410.0.0 ... 10.0.7 (8 versions)10.0.8—
Microsoft.AspNetCore.App.Runtime.win-x8610.0.0 ... 10.0.7 (8 versions)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 / 36× 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 117 total refreshes for this CVE.

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

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 in the National Vulnerability Database on May 12, 2026, with the most recent update on July 15, 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 82.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42899?
CVE-2026-42899 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-42899?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42899, 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-42899

Explore →

Is Your Infrastructure Affected by CVE-2026-42899?

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

Start Free Scan →Browse All CVEs