An Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability [CWE-22] in Fortinet FortiDLP Agent's Outlookproxy plugin for Windows 11.5.1 and 11.4.2 through 11.4.6 and 11.3.2 through 11.3.4 and 11.2.0 through 11.2.3 and 11.1.1 through 11.1.2 and 11.0.1 and 10.5.1 and 10.4.0, and 10.3.1 may allow an authenticated attacker to escalate their privilege to LocalService via sending a crafted request to a local listening port.
IBM MQ 9.1, 9.2, 9.3, 9.4 LTS and 9.3, 9.4 CD is vulnerable to a denial of service, caused by improper enforcement of the timeout on individual read operations. By conducting slowloris-type attacks, a remote attacker could exploit this vulnerability to cause a denial of service.
A malicious actor that has been granted Guest Operation Privileges https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-security/GUID-6A952214-0E5E-4CCF-9D2A-90948FF643EC.html in a target virtual machine may be able to elevate their privileges if that target virtual machine has been assigned a more privileged Guest Alias https://vdc-download.vmware.com/vmwb-repository/dcr-public/d1902b0e-d479-46bf-8ac9-cee0e31e8ec0/07ce8dbd-db48-4261-9b8f-c6d3ad8ba472/vim.vm.guest.AliasManager.html .
MITRE: CVE-2025-59489 Unity Gaming Engine Editor vulnerability
In Python before 3.10.3 on Windows, local users can gain privileges because the search path is inadequately secured. The installer may allow a local attacker to add user-writable directories to the system search path. To exploit, an administrator must have installed Python for all users and enabled PATH entries. A non-administrative user can trigger a repair that incorrectly adds user-writable paths into PATH, enabling search-path hijacking of other users and system services. This affects Python (CPython) through 3.7.12, 3.8.x through 3.8.12, 3.9.x through 3.9.10, and 3.10.x through 3.10.2.
In Python 3.6 through 3.6.10, 3.7 through 3.7.8, 3.8 through 3.8.4rc1, and 3.9 through 3.9.0b4 on Windows, a Trojan horse python3.dll might be used in cases where CPython is embedded in a native application. This occurs because python3X.dll may use an invalid search path for python3.dll loading (after PySetPath has been used). NOTE: this issue CANNOT occur when using python.exe from a standard (non-embedded) Python installation on Windows.
Insufficient initialization in Intel(R) SGX SDK Windows versions 2.4.100.51291 and earlier, and Linux versions 2.6.100.51363 and earlier, may allow an authenticated user to enable information disclosure, escalation of privilege or denial of service via local access.
Insufficient input validation in Intel(R) SGX SDK multiple Linux and Windows versions may allow an authenticated user to enable information disclosure, escalation of privilege or denial of service via local access.
.NET Denial of Service Vulnerability
.NET Denial of Service Vulnerability
.NET Remote Code Execution Vulnerability
.NET Framework Elevation of Privilege Vulnerability
.NET Framework Denial of Service Vulnerability
.NET Framework Remote Code Execution Vulnerability
.NET Framework Denial of Service Vulnerability
.NET Security Feature Bypass Vulnerability
.NET Denial of Service Vulnerability
.NET Tampering Vulnerability
Heap-based buffer overflow in Windows ALPC allows an authorized attacker to elevate privileges locally.
Improper privilege management in Windows Group Policy allows an authorized attacker to elevate privileges locally.
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows USB Driver allows an authorized attacker to elevate privileges locally.
.NET Core Remote Code Execution Vulnerability
.NET Elevation of Privilege Vulnerability
.NET Elevation of Privilege Vulnerability
.NET Elevation of Privilege Vulnerability
Microsoft Security Advisory CVE-2026-56170 – .NET Denial of Service Vulnerability
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core SignalR (Microsoft.AspNetCore.App.Runtime). This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A denial of service vulnerability exists in ASP.NET Core SignalR in .NET 8, .NET 9, and .NET 10. Stateful reconnect can be leveraged by an attacker to deny service to other users.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/TBD
CVSS Details
- Version: 3.1 - Severity: High - Score: 7.5 - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C - Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)
Affected Platforms
- Platforms: All - Architectures: All
Mitigation Factors
Your ASP.NET Core app is only affected if it uses SignalR with stateful reconnect enabled.
<a name="affected-packages"></a>Affected Packages The vulnerability affects any Microsoft .NET project if it uses any of affected package versions listed below
<a name=".NET 10.0"></a>.NET 10.0 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.linux-arm | >= 10.0.0, <= 10.0.5 | 10.0.6 Microsoft.AspNetCore.App.Runtime.linux-arm64 | >= 10.0.0, <= 10.0.5 | 10.0.6 Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >= 10.0.0, <= 10.0.5 | 10.0.6 Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >= 10.0.0, <= 10.0.5 | 10.0.6 Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >= 10.0.0, <= 10.0.5 | 10.0.6 Microsoft.AspNetCore.App.Runtime.linux-x64 | >= 10.0.0, <= 10.0.5 | 10.0.6 Microsoft.AspNetCore.App.Runtime.osx-arm64 | >= 10.0.0, <= 10.0.5 | 10.0.6 Microsoft.AspNetCore.App.Runtime.osx-x64 | >= 10.0.0, <= 10.0.5 | 10.0.6 Microsoft.AspNetCore.App.Runtime.win-arm | >= 10.0.0, <= 10.0.5 | 10.0.6 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 10.0.0, <= 10.0.5 | 10.0.6 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 10.0.0, <= 10.0.5 | 10.0.6 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 10.0.0, <= 10.0.5 | 10.0.6
<a name=".NET 9.0"></a>.NET 9.0 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.linux-arm | >= 9.0.0, <= 9.0.14 | 9.0.15 Microsoft.AspNetCore.App.Runtime.linux-arm64 | >= 9.0.0, <= 9.0.14 | 9.0.15 Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >= 9.0.0, <= 9.0.14 | 9.0.15 Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >= 9.0.0, <= 9.0.14 | 9.0.15 Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >= 9.0.0, <= 9.0.14 | 9.0.15 Microsoft.AspNetCore.App.Runtime.linux-x64 | >= 9.0.0, <= 9.0.14 | 9.0.15 Microsoft.AspNetCore.App.Runtime.osx-arm64 | >= 9.0.0, <= 9.0.14 | 9.0.15 Microsoft.AspNetCore.App.Runtime.osx-x64 | >= 9.0.0, <= 9.0.14 | 9.0.15 Microsoft.AspNetCore.App.Runtime.win-arm | >= 9.0.0, <= 9.0.14 | 9.0.15 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 9.0.0, <= 9.0.14 | 9.0.15 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 9.0.0, <= 9.0.14 | 9.0.15 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 9.0.0, <= 9.0.14 | 9.0.15
<a name=".NET 8.0"></a>.NET 8.0 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.linux-arm | >= 8.0.0, <= 8.0.25 | 8.0.26 Microsoft.AspNetCore.App.Runtime.linux-arm64 | >= 8.0.0, <= 8.0.25 | 8.0.26 Microsoft.AspNetCore.App.Runtime.linux-musl-arm | >= 8.0.0, <= 8.0.25 | 8.0.26 Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 | >= 8.0.0, <= 8.0.25 | 8.0.26 Microsoft.AspNetCore.App.Runtime.linux-musl-x64 | >= 8.0.0, <= 8.0.25 | 8.0.26 Microsoft.AspNetCore.App.Runtime.linux-x64 | >= 8.0.0, <= 8.0.25 | 8.0.26 Microsoft.AspNetCore.App.Runtime.osx-arm64 | >= 8.0.0, <= 8.0.25 | 8.0.26 Microsoft.AspNetCore.App.Runtime.osx-x64 | >= 8.0.0, <= 8.0.25 | 8.0.26 Microsoft.AspNetCore.App.Runtime.win-arm | >= 8.0.0, <= 8.0.25 | 8.0.26 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 8.0.0, <= 8.0.25 | 8.0.26 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 8.0.0, <= 8.0.25 | 8.0.26 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 8.0.0, <= 8.0.25 | 8.0.26
Advisory FAQ
<a name="how-affected"></a>How do I know if I am affected?
If using a package listed in affected packages, you're exposed to the vulnerability.
<a name="how-fix"></a>How do I fix the issue?
1. To fix the issue please install the latest version of .NET. 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 nuget package, update the package reference to the patched version. You can list the versions you have installed by running the dotnet --info command.
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 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. Further information can be found in the MSRC Report an Issue FAQ.
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.
External Links
CVE-2026-56170
Acknowledgements
Ky0toFu
Revisions
V1.0 (July 14, 2026): Advisory published.
.NET Framework Denial of Service Vulnerability
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Win32K allows an authorized attacker to elevate privileges locally.
Use after free in Microsoft Printer Drivers allows an authorized attacker to elevate privileges locally.
.NET Elevation of Privilege Vulnerability