IBM Langflow OSS 1.0.0 through 1.11.2 could allow a remote authenticated attacker to obtain sensitive information due to path traversal.

IBM Langflow OSS 1.0.0 through 1.11.2 could allow a remote attacker to obtain sensitive information due to incomplete scrubbing of sensitive credential fields.

IBM Langflow OSS 1.0.0 through 1.11.2 could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery.

IBM Langflow OSS 1.0.0 through 1.11.2 could allow a remote authenticated attacker to obtain sensitive information due to improper validation of symbolic links.

IBM Langflow OSS 1.0.0 through 1.11.2 could allow a remote authenticated attacker to delete arbitrary local files or directories due to improper limitation of a pathname to a restricted directory.

IBM Langflow OSS 1.0.0 through 1.11.2 could allow a remote authenticated attacker to obtain sensitive information from internal services due to a URL parser discrepancy.

IBM Langflow OSS 1.0.0 through 1.11.2 could allow a remote attacker to obtain sensitive information due to server-side request forgery.

IBM Langflow OSS 1.0.0 through 1.11.2 allows an authenticated attacker to read arbitrary files from the server filesystem — including server secret material (secretkey, JWT signing keys, the application database, /proc/self/environ, and other tenants' upload directories) — by supplying absolute paths or traversal sequences in the files parameter of an authenticated build request. The file contents were embedded as text attachments in the language model prompt and transmitted to the configured model endpoint, resulting in confidential data exfiltration. This bypassed the LANGFLOWRESTRICTLOCALFILEACCESS=true containment boundary, which was enforced for other file-reading components but not for the Chat Input to Message attachment pipeline.

IBM Langflow OSS 1.0.0 through 1.11.2 suffer from a stored cross-site scripting vulnerability in the Playground chat interface.

IBM Langflow OSS 1.0.0 through 1.11.2 Langflow could allow an authenticated attacker to write arbitrary files to the server due to improper input validation in the SaveToFileComponent. The application constructs local file paths using attacker‑controlled input without sufficient sanitization when handling requests to the /api/v1/run/{flowid} endpoint. An attacker with low‑privileged authenticated access (such as a valid API key or user session) can supply crafted path values, including absolute paths or path traversal sequences, allowing arbitrary file writes to locations writable by the Langflow process. Successful exploitation may lead to unauthorized file creation or modification, potentially resulting in further compromise depending on the deployment environment.

IBM Langflow OSS 1.0.0 through 1.11.2 allows remote authenticated attackers to bypass localhost-only MCP configuration installation by spoofing X-Forwarded-For: 127.0.0.1 header, enabling arbitrary writes to IDE config files (~/.cursor/mcp.json, etc.).

IBM Langflow OSS 1.0.0 through 1.11.2 could allow a remote authenticated attacker to execute arbitrary code due to an authorization bypass in the flow build process.

.NET Information Disclosure Vulnerability

In the Linux kernel, the following vulnerability has been resolved:

posix-cpu-timers: fix race between handleposixcputimers() and posixcputimerdel()

If an exiting non-autoreaping task has already passed exitnotify() and calls handleposixcputimers() from IRQ, it can be reaped by its parent or debugger right after unlocktasksighand().

If a concurrent posixcputimerdel() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cputimertaskrcu() and/or locktasksighand() will fail.

Add the tsk->exitstate check into runposixcputimers() to fix this.

This fix is not needed if CONFIGPOSIXCPUTIMERSTASKWORK=y, because exittaskwork() is called before exitnotify(). But the check still makes sense, taskworkadd(&tsk->posixcputimerswork.work) will fail anyway in this case.

.NET Elevation of Privilege Vulnerability

.NET Elevation of Privilege Vulnerability

.NET Elevation of Privilege Vulnerability

.NET Denial of Service Vulnerability

.NET Security Feature Bypass Vulnerability

.NET Denial of Service Vulnerability

.NET Spoofing Vulnerability

.NET Denial of Service Vulnerability

.NET Framework Denial of Service Vulnerability

.NET Framework Denial of Service Vulnerability

.NET Security Feature Bypass Vulnerability

.NET Denial of Service Vulnerability

.NET Tampering Vulnerability

.NET Security Feature Bypass 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