Skip to main content

CVE-2026-66822: CWE-201: Insertion of Sensitive Information Into Sent Data in Microsoft .NET 10.0

0
Medium
Published: 10/13/2026 (10/13/2026, 18:59:44 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: .NET 10.0

Description

Insertion of sensitive information into sent data in .NET allows an unauthorized attacker to disclose information over a network.

CVSS v3.1

Score 5.9medium

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C

Affected software

Microsoft

.NET 10.0

Affected versions
>=10.0.0 <10.0.13

Microsoft

.NET 11.0

Affected versions
>=11.0.0 <11.0.0-rc.2

Microsoft

.NET 8.0

Affected versions
>=8.0.0 <8.0.32

Microsoft

.NET 9.0

Affected versions
>=9.0.0 <9.0.21

Microsoft

Microsoft Visual Studio 2022 version 17.14

Affected versions
>=17.14.0 <17.14.42

Microsoft

Microsoft Visual Studio 2026 version 18.10

Affected versions
>=18.10.0 <18.10.4

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/13/2026, 21:58:09 UTC

Technical Analysis

This vulnerability (CWE-201) in Microsoft .NET's System.Net.Http occurs because the SocketsHttpHandler can retain and send the Proxy-Authorization header during HTTP redirects, which can cause sensitive proxy credentials to be leaked to the redirected destination server. The vulnerability affects multiple runtime packages across various platforms and architectures. The CVSS 3.1 score is 5.9 (medium severity) with network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact. Official patches have been released to fix this issue in affected versions.

Potential Impact

The vulnerability can lead to the unintended disclosure of sensitive proxy credentials (basic authentication) to destination servers following HTTP redirects. This compromises confidentiality but does not affect integrity or availability. There are no known exploits in the wild at this time.

Mitigation Recommendations

Microsoft has released official fixes for this vulnerability. Users and developers should update affected Microsoft .NET runtime packages to the patched versions listed by Microsoft to remediate the issue. No additional mitigation steps are required beyond applying the official updates.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
microsoft
Date Reserved
2026-07-27T19:02:26.602Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
official-fix
Vendor Advisory Urls
[{"url":"https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-66822","vendor":"Microsoft"}]

Threat ID: 6ace84a72cdf04f6569f0c37

Added to database: 10/13/2026, 19:21:11 UTC

Last enriched: 10/13/2026, 21:58:09 UTC

Last updated: 10/13/2026, 22:50:42 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses