CVE-2023-38180

CRITICALNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-08-09), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 14%CVSS: 7.5Exploit: cisa kev · ssvc active · epss top5pctExposed services: Not assessed

A fix is available — apply it.

.NET and Visual Studio Denial of Service Vulnerability

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
96
EG Risk 96/100CISA SSVC

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
Severity90% × 45%
Exploitation100% × 40%
Automatability100% × 15%
CISA SSVC: Attend at low or medium mission impact; Act at high (mission-essential systems).
Action: A fix is available. Apply it sooner than your standard update timelines at low or medium mission impact and as soon as possible at high.
EPSS PROB
14%
EPSS %ILE
96th
KEV
⚠ Exploited

CISA SSVCAttend at low or medium mission impact; Act at high (mission-essential systems).

A fix is available. Apply it sooner than your standard update timelines at low or medium mission impact and as soon as possible at high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 8, 2023

Last Modified

August 10, 2026

Advisory Details (4)

Auto-updated Jun 4, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft, cisa.
cisa🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-38180
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-2023-38180
generic

[SECURITY] Fedora 37 Update: dotnet7.0-7.0.110-1.fc37 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/NWVZFKTLNMNKPZ755EMRYIA6GHFOWGKY/
generic

[SECURITY] Fedora 38 Update: dotnet7.0-7.0.110-1.fc38 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/CL2L4WE5QRT7WEXANYXSKSU43APC5N2V/

Vendor Advisories for CVE-2023-38180(1)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunetstandard-targeting-pack-2.1-7.0 (7.0.110-0ubuntu1~23.04.1) @ lunar2026-10-10ubuntu
ubuntunetstandard-targeting-pack-2.1-7.0 (7.0.110-0ubuntu1~22.04.1) @ jammy2026-10-10ubuntu
redhatdotnet6.0-0:6.0.121-1.el9_02023-08-14redhat
redhatdotnet6.0-0:6.0.121-1.el8_82023-08-14redhat
redhatdotnet7.0-0:7.0.110-1.el9_22023-08-14redhat
redhatrh-dotnet60-dotnet-0:6.0.121-1.el7_92023-08-14redhat
redhatdotnet7.0-0:7.0.110-1.el8_82023-08-14redhat
redhatdotnet6.0-0:6.0.121-1.el9_22023-08-14redhat
redhatdotnet6.0-0:6.0.121-1.el8_62023-08-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

(5 across 1 ecosystem)
NuGet(5)
PackageVulnerable rangeFix by version rangeDependents
Microsoft.AspNetCore.App.Runtime.win-arm646.0.0 ... 6.0.9 (20 versions)
  • 7.0.0 up to 7.0.10: fixed in 7.0.10
  • 6.0.0 up to 6.0.21: fixed in 6.0.21
—
Microsoft.AspNetCore.App.Runtime.win-x646.0.0 ... 6.0.9 (20 versions)
  • 7.0.0 up to 7.0.10: fixed in 7.0.10
  • 6.0.0 up to 6.0.21: fixed in 6.0.21
—
Microsoft.AspNetCore.App.Runtime.win-x866.0.0 ... 6.0.9 (20 versions)
  • 7.0.0 up to 7.0.10: fixed in 7.0.10
  • 6.0.0 up to 6.0.21: fixed in 6.0.21
—
Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv0.0.1-alpha ... 2.1.3 (15 versions)
  • 6.0.0 up to 6.0.21: fixed in 6.0.21
  • every version up to 2.1.40: fixed in 2.1.40
—
Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets0.0.1-alpha ... 2.1.3 (10 versions)
  • every version up to 2.1.40: fixed in 2.1.40
—

Weakness Classification(1)

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

Additional Vendor Advisories

(9)

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 55× in last 7d / 244× 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 1,096 total refreshes for this CVE.

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

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

Same vendor

2 shown

redhat:RHSA-2023:4639 · ubuntu:USN-6278-1

Frequently asked(6)

What is CVE-2023-38180?
CVE-2023-38180 is a critical vulnerability published on August 8, 2023. .NET and Visual Studio Denial of Service Vulnerability
When was CVE-2023-38180 disclosed?
CVE-2023-38180 was first published on August 8, 2023, 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-2023-38180 actively exploited?
Yes. CISA added CVE-2023-38180 to the Known Exploited Vulnerabilities catalog on August 9, 2023, affecting Microsoft .NET Core and Visual Studio. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2023-38180?
CVE-2023-38180 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2023-38180?
CVE-2023-38180 affects Microsoft .NET Core and Visual Studio. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2023-38180?
A fix for CVE-2023-38180 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-38180 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-2023-38180

Explore →

Is Your Infrastructure Affected by CVE-2023-38180?

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

Book a Demo →Browse All CVEs