CVE-2026-32178

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: 0.1%, top 82% 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.

Improper neutralization of special elements in .NET allows an unauthorized attacker to perform spoofing over a network.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
81.3%
KEV
Not listed

Published

April 14, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated May 7, 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-32178

Vendor Advisories for CVE-2026-32178(13)

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

Patch Availability(19)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunetstandard-targeting-pack-2.1-9.0 (9.0.116-0ubuntu1~25.10.1) @ questing2026-06-14ubuntu
ubuntudotnet10 (10.0.107-10.0.7-0ubuntu1~26.04.1) @ resolute2026-06-14ubuntu
redhatdotnet8.0-0:8.0.126-1.el9_42026-05-05redhat
redhatdotnet8.0-0:8.0.126-1.el9_62026-05-04redhat
redhatdotnet9.0-0:9.0.116-1.el9_62026-05-04redhat
redhatdotnet9.0-0:9.0.116-1.el10_02026-05-04redhat
redhatdotnet8.0-0:8.0.126-1.el10_02026-05-04redhat
redhatdotnet9-0-main-9.0.116-1.hum12026-04-21redhat
redhatdotnet10-0-main-10.0.106-1.hum12026-04-20redhat
redhatdotnet8-0-main-8.0.126-1.hum12026-04-20redhat
redhatdotnet8.0-0:8.0.126-1.el9_72026-04-16redhat
redhatdotnet10.0-0:10.0.106-1.el9_72026-04-16redhat
redhatdotnet10.0-0:10.0.106-1.el10_12026-04-16redhat
redhatdotnet8.0-0:8.0.126-1.el8_102026-04-16redhat
redhatdotnet10.0-0:10.0.106-1.el8_102026-04-16redhat
redhatdotnet9.0-0:9.0.116-1.el8_102026-04-16redhat
redhatdotnet9.0-0:9.0.116-1.el9_72026-04-16redhat
redhatdotnet8.0-0:8.0.126-1.el10_12026-04-16redhat
redhatdotnet9.0-0:9.0.116-1.el10_12026-04-16redhat

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.NetCore.App.Runtime.linux-arm8.0.0 ... 8.0.8 (25 versions)8.0.26—
Microsoft.NetCore.App.Runtime.linux-arm648.0.0 ... 8.0.8 (25 versions)8.0.26—
Microsoft.NetCore.App.Runtime.linux-musl-arm8.0.0 ... 8.0.8 (25 versions)8.0.26—
Microsoft.NetCore.App.Runtime.linux-musl-arm648.0.0 ... 8.0.8 (25 versions)8.0.26—
Microsoft.NetCore.App.Runtime.linux-musl-x648.0.0 ... 8.0.8 (25 versions)8.0.26—
Microsoft.NetCore.App.Runtime.linux-x648.0.0 ... 8.0.8 (25 versions)8.0.26—
Microsoft.NetCore.App.Runtime.osx-arm648.0.0 ... 8.0.8 (25 versions)8.0.26—
Microsoft.NetCore.App.Runtime.osx-x648.0.0 ... 8.0.8 (25 versions)8.0.26—
Microsoft.NetCore.App.Runtime.win-arm—8.0.26—
Microsoft.NetCore.App.Runtime.win-arm648.0.0 ... 8.0.8 (25 versions)8.0.26—
Microsoft.NetCore.App.Runtime.win-x648.0.0 ... 8.0.8 (25 versions)8.0.26—
Microsoft.NetCore.App.Runtime.win-x868.0.0 ... 8.0.8 (25 versions)8.0.26—

Weakness Classification(1)

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

Additional Vendor Advisories

(7)

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 13× in last 7d / 45× 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 121 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-32178?
CVE-2026-32178 is a high vulnerability published on April 14, 2026. Improper neutralization of special elements in .NET allows an unauthorized attacker to perform spoofing over a network.
When was CVE-2026-32178 disclosed?
CVE-2026-32178 was first published in the National Vulnerability Database on April 14, 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-32178 actively exploited?
CVE-2026-32178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 81.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-32178?
CVE-2026-32178 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-32178?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32178, 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-32178

Explore →

Is Your Infrastructure Affected by CVE-2026-32178?

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

Start Free Scan →Browse All CVEs