.NET Information Disclosure Vulnerability

Exploitation

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

CVSS

5.8 · CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2022-41064: 0.84% estimated exploitation activity in the next 30 days; percentile 57.96 (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.

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET, .NET Core and .NET Framework's System.Data.SqlClient and Microsoft.Data.SqlClient NuGet Packages. A vulnerability exists in System.Data.SqlClient and Microsoft.Data.SqlClient libraries where a timeout occurring under high load can cause incorrect data to be returned as the result of an asynchronously executed query. <a name="mitigation-factors"</aMitigation factors If you are not talking to Microsoft SQL Server from your application you are not affected by this vulnerability. <a name="how-affected"</aHow do I know if I am affected? .NET has two types of dependencies: direct and transitive. Direct dependencies are dependencies where you specifically add a package to your project, transitive dependencies occur when you add a package to your project that in turn relies on another package. For example, the Microsoft.AspNetCore.Mvc package depends on the Microsoft.AspNetCore.Mvc.Core…

Published by the source

8 Nov 2022, 23:00 UTC

Last modified by the source

30 Jan 2023, 23:02 UTC

Source last checked

26 Oct 2026, 16:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8g2p-5pqh-5jmc

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

# Patch Next advisory brief: CVE-2022-41064

Advisory: .NET Information Disclosure Vulnerability
IDs: CVE-2022-41064, GHSA-8g2p-5pqh-5jmc
Record: https://patchnext.com/advisories/cve-2022-41064 (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: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: system.data.sqlclient 4.8.5; microsoft.data.sqlclient 2.1.2, 1.1.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet system.data.sqlclient: affected <= 4.8.4; fixed in 4.8.5
- NuGet microsoft.data.sqlclient: affected <= 1.1.3; >= 2.0.0, < 2.1.2; fixed in 1.1.4, 2.1.2

## Suggested inspection (read-only)
- NuGet system.data.sqlclient: check the installed version with your package manager.
- NuGet microsoft.data.sqlclient: 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 system.data.sqlclient, microsoft.data.sqlclient.
- 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-8g2p-5pqh-5jmc (GitHub-reviewed advisory GHSA-8g2p-5pqh-5jmc lists affected ranges: NuGet microsoft.data.sqlclient >=0 =2.0.0 =0 <=4.8.4)

Commands are suggestions: review each one before running it.