Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

.NET Tampering Vulnerability

cve-program · CVE-2026-45491

Published

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

Read the publisher's advisory

euvd · EUVD-2026-35675

Published

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

Read the publisher's advisory

nvd · CVE-2026-45491

Published

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

Read the publisher's advisory

osv · GHSA-7q4v-2mr6-5gpx

Published

## Executive Summary Microsoft is releasing this security advisory to provide information about a vulnerability in System.Formats.Tar. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A tampering vulnerability exists in the `TarFile.ExtractToDirectory` method where a symlink path traversal enables an attacker to perform arbitrary file writes outside the intended extraction directory. ## Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/404 ## Affected Platforms - **Platforms:** All - **Architectures:** All ## Affected Packages The vulnerability affects any Microsoft .NET project if it uses any of affected package versions listed below ### .NET 10 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- [Microsoft.NETCore.App.Runtime](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime) | >= 10.0.0, <= 10.0.8 | 10.0.9 ### .NET 9 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- [Microsoft.NETCore.App.Runtime](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime) | >= 9.0.0, <= 9.0.16 | 9.0.17 ### .NET 8 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- [Microsoft.NETCore.App.Runtime](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime) | >= 8.0.0, <= 8.0.27 | 8.0.28 ## Advisory FAQ ### How do I know if I am affected? If using a package listed in affected packages, you're exposed to the vulnerability. ### How do I fix the issue? 1. To fix the issue please install the latest version of .NET 8.0, .NET 9.0, or .NET 10.0, as appropriate. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs. 2. If your application references the vulnerable package, update the package reference to the patched version. Once you have installed the updated runtime or SDK, restart your apps for the update to take effect. Additionally, if you've deployed [self-contained applications](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. ## Other Information ### Reporting Security Issues If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the [MSRC Researcher Portal](https://msrc.microsoft.com/report/vulnerability/new). Further information can be found in the MSRC [Report an Issue FAQ](https://www.microsoft.com/msrc/faqs-report-an-issue). Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty. ### Support You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue. ### Disclaimer The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. ### Acknowledgements Anonymous, Ashmit Sharma, Ky0toFu ,phrolo7a ### Revisions V1.0 (June 9, 2026): Advisory published.

Read the publisher's advisory

Affected versions, risk 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-2026-45491

This is a saved version of the risk data. The advisory details have their own history. Latest risk data.

No CISA KEV listing is included in this saved record. Exploitation may still have occurred.

FIRST EPSS: 0.39 % · percentile 33.25 % · scored 10 Nov 2026. This score is more than two days old.

Saved 10 Nov 2026 20:24:10 UTC · View this risk record (JSON)

Advisory history

15 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.

16 Nov 2026 01:10:46 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

euvd · EUVD-2026-35675 · Published

14 Nov 2026 00:08:49 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

euvd · EUVD-2026-35675 · Published

12 Nov 2026 17:18:54 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

nvd · CVE-2026-45491 · Published

11 Nov 2026 12:03:09 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

euvd · EUVD-2026-35675 · Published

9 Nov 2026 11:07:50 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

euvd · EUVD-2026-35675 · Published

7 Nov 2026 10:34:53 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

euvd · EUVD-2026-35675 · Published

5 Nov 2026 10:00:21 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

euvd · EUVD-2026-35675 · Published

3 Nov 2026 09:04:55 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

euvd · EUVD-2026-35675 · Published

1 Nov 2026 08:11:18 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

euvd · EUVD-2026-35675 · Published

30 Oct 2026 07:56:45 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

euvd · EUVD-2026-35675 · Published

28 Oct 2026 06:11:32 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

euvd · EUVD-2026-35675 · Published

25 Oct 2026 10:17:33 UTC

Improper link resolution before file access ('link following') in .NET allows an unauthorized attacker to perform tampering locally.

nvd · CVE-2026-45491 · Published

23 Oct 2026 16:01:25 UTC

Microsoft Security Advisory CVE-2026-45491 – .NET Tampering Vulnerability

osv · GHSA-7q4v-2mr6-5gpx · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 06:51 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current