CVE-2023-38180CISA KEV

Microsoft .NET Core and Visual Studio Denial-of-Service Vulnerability

Severity unknownCVSS unknownCheck the vendor advisory for fixed versions

CISA lists this Microsoft vulnerability as known exploited. Its MSRC release detail is outside this installation's collected history.

CISA KEV Check MSRC

CISA catalog record

Microsoft .NET Core and Visual Studio contain an unspecified vulnerability that allows for denial-of-service (DoS).

Product: .NET Core and Visual Studio
Added to KEV: 9 Aug 2023
Federal remediation due: 30 Aug 2023
Known ransomware use: Not reported

Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version

Field-level log (2)

Up to 100 recent field edits are shown; older edits may be outside retention.

23 Oct 2026 · 09:33:49 UTC Source coverage: cisa-kevIncomplete → Current
23 Oct 2026 · 08:31:50 UTC Source coverage: cisa-kevCurrent → Incomplete

Explore global source statements, affected packages and advisory history for CVE-2023-38180. The catalog has a separate collection scope from Microsoft release records.

More advisories, affected versions and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

CVE-2023-38180

Listed in CISA KEV · added 9 Aug 2023 · Microsoft · .NET Core and Visual Studio

Microsoft .NET Core and Visual Studio contain an unspecified vulnerability that allows for denial-of-service (DoS).

CISA source

FIRST EPSS: 14.13 % · percentile 96.63 % · scored 13 Nov 2026.

Saved 13 Nov 2026 19:59:34 UTC · View this risk record (JSON)

Risk history

Compare earlier KEV listings and daily EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Other daily score changes remain in this history.

CVE-2023-38180 · 13 Nov 2026 19:59:34 UTC

CVE-2023-38180 · 12 Nov 2026 18:18:51 UTC

CVE-2023-38180 · 10 Nov 2026 20:24:10 UTC

CVE-2023-38180 · 09 Nov 2026 21:04:24 UTC

CVE-2023-38180 · 08 Nov 2026 15:12:21 UTC

CVE-2023-38180 · 07 Nov 2026 16:07:52 UTC

CVE-2023-38180 · 06 Nov 2026 19:10:17 UTC

CVE-2023-38180 · 05 Nov 2026 22:49:22 UTC

CVE-2023-38180 · 05 Nov 2026 02:54:06 UTC

CVE-2023-38180 · 03 Nov 2026 16:59:18 UTC

CVE-2023-38180 · 02 Nov 2026 23:59:04 UTC

CVE-2023-38180 · 01 Nov 2026 23:58:58 UTC

CVE-2023-38180 · 01 Nov 2026 03:04:52 UTC

CVE-2023-38180 · 31 Oct 2026 01:52:30 UTC

CVE-2023-38180 · 29 Oct 2026 18:29:26 UTC

CVE-2023-38180 · 28 Oct 2026 19:55:37 UTC

CVE-2023-38180 · 27 Oct 2026 15:46:19 UTC

CVE-2023-38180 · 27 Oct 2026 00:23:05 UTC

CVE-2023-38180 · 25 Oct 2026 15:18:41 UTC

CVE-2023-38180 · 25 Oct 2026 02:24:38 UTC

CVE-2023-38180 · 23 Oct 2026 16:01:26 UTC

Advisory history

13 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

12 Nov 2026 04:59:15 UTC