Denial of service in ASP.NET Core

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2018-8269: 26.80% estimated exploitation activity in the next 30 days; percentile 98.03 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A denial of service vulnerability exists when OData Library improperly handles web requests, aka "OData Denial of Service Vulnerability." This affects Microsoft.Data.OData.

Published by the source

16 Oct 2018, 19:58 UTC

Last modified by the source

7 Jan 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mv2r-q4g5-j8q5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2018-8269

Advisory: Denial of service in ASP.NET Core
IDs: CVE-2018-8269, GHSA-mv2r-q4g5-j8q5
Record: https://patchnext.com/advisories/cve-2018-8269 (revision 1, source checked 26 Oct 2026, 16:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: microsoft.data.odata 5.8.4; microsoft.aspnetcore.all 2.2.7, 2.1.13; microsoft.aspnetcore.dataprotection.azurestorage 2.2.7, 2.1.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet microsoft.data.odata: affected < 5.8.4; fixed in 5.8.4
- NuGet microsoft.aspnetcore.all: affected >= 2.1.0, < 2.1.13; >= 2.2.0, < 2.2.7; fixed in 2.2.7, 2.1.13
- NuGet microsoft.aspnetcore.dataprotection.azurestorage: affected >= 2.1.0, < 2.1.13; >= 2.2.0, < 2.2.7; fixed in 2.2.7, 2.1.13

## Suggested inspection (read-only)
- NuGet microsoft.data.odata: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.all: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.dataprotection.azurestorage: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on microsoft.data.odata, microsoft.aspnetcore.all, microsoft.aspnetcore.dataprotection.azurestorage.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mv2r-q4g5-j8q5 (GitHub-reviewed advisory GHSA-mv2r-q4g5-j8q5 lists affected ranges: NuGet microsoft.data.odata >=0 =2.1.0 =2.2.0 =2.1.0 =2.2.0 <2.2.7)

Commands are suggestions: review each one before running it.