CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-62899

CVE-2026-62899: .NET Security Feature Bypass Vulnerability (HTTP Request Smuggling)

Amit Schendel
Amit Schendel
Senior Security Researcher

Aug 12, 2026·6 min read·166 visits

Executive Summary (TL;DR)

A medium-severity HTTP request smuggling vulnerability in .NET on Linux and macOS allows unauthenticated remote attackers to bypass frontend security policies, hijack active user sessions, and cause cache desynchronization.

CVE-2026-62899 is a security feature bypass vulnerability in the Microsoft .NET runtime environment on non-Windows platforms. The flaw manifests as an HTTP Request/Response Smuggling vulnerability (CWE-444) within the managed implementation of the System.Net.HttpListener class. This allows unauthenticated remote attackers to desynchronize request boundaries when the backend .NET application is hosted behind an upstream reverse proxy.

Vulnerability Overview

CVE-2026-62899 represents a security feature bypass vulnerability in the Microsoft .NET runtime environment on non-Windows platforms. The flaw arises from an HTTP Request/Response Smuggling vulnerability, classified as CWE-444, within the managed implementation of the System.Net.HttpListener class.

While Windows implementations delegate HTTP parsing to the robust, kernel-level http.sys driver, non-Windows systems (including Linux and macOS) rely on a custom, managed C# HTTP parser. This architectural difference introduces discrepancies in how HTTP request boundaries are parsed and validated compared to upstream reverse proxies like Nginx or HAProxy.

An unauthenticated remote attacker can exploit these parsing inconsistencies to desynchronize the connection boundaries between the reverse proxy and the backend .NET server. This desynchronization enables the attacker to inject a hidden secondary request within the body of a primary request, leading to security control bypasses or unauthorized data exposure.

Root Cause Analysis

The root cause of CVE-2026-62899 lies in inconsistent parsing logic and character normalization routines inside the managed C# HTTP parser of System.Net.HttpListener. When the parser processes incoming headers, it handles whitespaces and character normalization in an overly permissive manner, deviating from strict RFC standards.

Specifically, the managed parser's integration with ICU (International Components for Unicode) globalization libraries created a normalization vulnerability. If HTTP headers are validated using culture-aware string methods rather than strict, binary-level ordinal checks, certain full-width Unicode characters can be normalized into standard ASCII control characters like colons or line endings. This allows an attacker to construct headers that appear benign to an upstream proxy but are interpreted as structural boundaries by the backend .NET runtime.

Furthermore, the parser failed to strictly enforce RFC 9112 rules regarding trailing and leading whitespaces in header fields, particularly around the colon delimiter. The permissive handling of malformed headers (such as Transfer-Encoding : chunked) allows an attacker to cause a desynchronization where the frontend proxy ignores the header due to strict validation, while the backend processes it, or vice versa.

Code Analysis

The remediation of this vulnerability required updating key parsing components and upgrading native and managed dependencies within the .NET runtime. Developers resolved the ICU normalization issue by enforcing strict ASCII/ordinal string comparisons on all HTTP header fields, preventing Unicode normalization side-channels.

In addition, native transport libraries were upgraded to enforce stricter boundary validation. The native MsQuic library was bumped from version 2.4.18 to 2.5.9 within the eng/Versions.props file to resolve potential state machine issues in HTTP/3 transport processing. The following diff highlights the dependency transitions implemented in the servicing branch:

<!-- eng/Versions.props -->
<Project>
  <PropertyGroup>
-   <MicrosoftNativeQuicMsQuicSchannelVersion>2.4.18</MicrosoftNativeQuicMsQuicSchannelVersion>
+   <MicrosoftNativeQuicMsQuicSchannelVersion>2.5.9</MicrosoftNativeQuicMsQuicSchannelVersion>
  </PropertyGroup>
</Project>

The Microsoft.NETCore.Runtime.ICU.Transport package was also updated across multiple cycles to secure the globalization boundary. Specifically, the package version was rolled from 10.0.0-rtm.26313.1 to 10.0.0-rtm.26364.2 to eliminate character-mapping discrepancies.

Exploitation Methodology

Exploiting CVE-2026-62899 requires a deployment scenario where the backend .NET application is hosted on Linux or macOS behind an affected frontend reverse proxy. The attacker targets the connection state using standard HTTP Request Smuggling vectors, such as CL.TE or TE.CL.

In a CL.TE scenario, the attacker transmits a single TCP payload containing a standard Content-Length header and a malformed Transfer-Encoding : chunked header with a trailing whitespace. The frontend proxy, validating strictly, reads the request according to the Content-Length field and forwards the entire stream. The backend .NET parser, being overly permissive, normalizes the malformed Transfer-Encoding header and treats the body as chunked data.

When the backend server encounters the terminating chunk (0), it concludes the processing of the first request. The remaining bytes in the connection buffer are then parsed as a new, separate HTTP request. This secondary, smuggled request executes in the context of the established TCP connection, bypassing access lists enforced by the frontend proxy.

Impact Assessment

The impact of a successful HTTP request smuggling exploit is classified as high for confidentiality. An attacker who successfully desynchronizes a persistent connection can intercept and manipulate the requests and responses of other users sharing that connection.

This capability allows the attacker to hijack active sessions by capturing sensitive headers, authorization tokens, or session cookies. Additionally, if a caching proxy is utilized in the architecture, the attacker can execute web cache poisoning attacks, storing malicious responses on the proxy to be served to subsequent legitimate users.

From a CVSS perspective, the vulnerability receives a base score of 5.9 (Medium). The score reflects high confidentiality impact but zero direct integrity or availability impact because the vulnerability does not natively permit code execution or persistent data modification. However, the downstream impact of session hijacking can lead to complete application compromise.

Remediation & Mitigation Guidance

Resolving CVE-2026-62899 requires updating the .NET SDK and runtime to the latest patched servicing releases. Organizations running applications on Linux or macOS must upgrade to .NET 10.0.11, .NET 9.0.19, or .NET 8.0.30 immediately to receive the secure HTTP parser implementation.

Where immediate patching of the runtime is unfeasible, several mitigating controls can be implemented. Administrators should configure their frontend reverse proxies (such as Nginx or HAProxy) to normalize incoming HTTP headers strictly, ensuring that requests containing conflicting framing or non-standard whitespaces are rejected before reaching the backend.

Alternatively, disabling connection keep-alives at the reverse proxy or backend level will mitigate the threat of smuggling by forcing the termination of the TCP connection after each request. However, this mitigation is not recommended as a long-term solution because it introduces significant latency and processing overhead due to repeated TCP handshakes.

Official Patches

MicrosoftMSRC Security Advisory

Fix Analysis (3)

Technical Appendix

CVSS Score
5.9/ 10
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 Systems

.NET Runtime on Linux.NET Runtime on macOS.NET Runtime on WebAssembly

Affected Versions Detail

Product
Affected Versions
Fixed Version
Microsoft .NET 10.0
Microsoft
>= 10.0.0, < 10.0.1110.0.11
Microsoft .NET 9.0
Microsoft
>= 9.0.0, < 9.0.199.0.19
Microsoft .NET 8.0
Microsoft
>= 8.0.0, < 8.0.308.0.30
Microsoft Visual Studio 2022 (version 17.14)
Microsoft
>= 17.14.0, < 17.14.3817.14.38
Microsoft Visual Studio 2026 (version 18.8)
Microsoft
>= 18.0, < 18.8.318.8.3
AttributeDetail
CWE IDCWE-444
Attack VectorNetwork (AV:N)
Attack ComplexityHigh (AC:H)
CVSS Base Score5.9 (Medium)
Exploit StatusNo active public exploits
KEV StatusNot Listed

MITRE ATT&CK Mapping

T1190Exploit Public-Facing Application
Initial Access
CWE-444
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Vulnerability Timeline

CVE Published
2026-08-11

References & Sources

  • [1]Microsoft Security Update Guide
  • [2]NVD - CVE-2026-62899
  • [3]dotnet/runtime Commit 18c88378

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•13 minutes ago•CVE-2026-122244
7.7

CVE-2026-122244: Stored Cross-Site Scripting in Budibase Builder Formula Evaluation

CVE-2026-122244 (GHSA-r2q3-7m4h-63qg) is a high-severity cross-privilege Stored Cross-Site Scripting (XSS) vulnerability in Budibase prior to version 3.50.0. The flaw occurs due to defective character escaping in the JSON formatter utility combined with raw HTML rendering via Svelte's {@html} directive in the Budibase Builder interface. A low-privileged application user or an unauthenticated form visitor can store malicious HTML markup in a shared datasource, which subsequently executes arbitrary JavaScript in the browser session of an administrator or application builder inspecting Handlebars formula bindings.

Amit Schendel
Amit Schendel
1 views•9 min read
•about 1 hour ago•CVE-2026-122247
8.2

CVE-2026-122247: Unauthenticated Global-Admin and Database Creation via Tenant-Confusion Bypass in Budibase

A tenant-confusion vulnerability in the user initialization endpoint of the Budibase worker service (prior to version 3.50.0) allows unauthenticated remote attackers to bypass the one-time administrative setup guard. By supplying arbitrary tenant identifiers in POST requests to /api/global/users/init, an attacker can force the underlying CouchDB datastore to dynamically provision unlimited tenant databases and persist latent global administrator accounts. This results in datastore resource exhaustion, denial of service, and unauthorized administrative account creation inside non-default tenant contexts.

Amit Schendel
Amit Schendel
2 views•9 min read
•about 2 hours ago•CVE-2026-103026
8.1

CVE-2026-103026: Arbitrary Method Invocation and State Tampering in Paymenter via Livewire HasConfirmation Trait

Paymenter versions prior to 1.5.7 contain an arbitrary method invocation vulnerability within the base Livewire component architecture. The application includes a legacy trait, HasConfirmation, inside app/Livewire/Component.php, which is inherited across 36 client-facing Livewire components. This trait exposes a public remote procedure call (RPC) endpoint named executeConfirmedAction without access controls or method allowlisting. Remote attackers can invoke arbitrary methods on any inheriting component, including Livewire's internal fill() method, enabling them to bypass #[Locked] property protections and manipulate internal component state and hydrated Eloquent models.

Alon Barad
Alon Barad
2 views•9 min read
•about 3 hours ago•CVE-2026-104885
6.3

CVE-2026-104885: Cross-Realm MQTT Session Disconnect via Missing Authorization in OpenRemote

OpenRemote prior to version 1.31.0 contains a Missing Authorization vulnerability (CWE-862) in the user management REST API endpoint responsible for disconnecting active MQTT sessions. The disconnectUserSession method in UserResourceImpl fails to verify whether the requesting user owns the target MQTT session, holds administrative privileges, or belongs to the realm specified in the request path. As a result, any authenticated user who obtains a valid MQTT session identifier can forcefully terminate active MQTT connections belonging to other users or IoT devices across any tenant realm.

Amit Schendel
Amit Schendel
2 views•9 min read
•about 4 hours ago•CVE-2026-69133
5.3

CVE-2026-69133: Cumulation Buffer Memory Retention in Netty OHTTP Codec

CVE-2026-69133 (GHSA-cg26-4c6j-2x8h) is a missing resource release vulnerability (CWE-772) in io.netty.incubator:netty-incubator-codec-ohttp affecting versions 0.0.20.Final through 0.0.26.Final. Both OHttpClientCodec and OHttpServerCodec retain the outer cumulationBuffer at its expanded high-water capacity after an Oblivious HTTP (OHTTP) exchange finishes. A remote unauthenticated attacker can complete a large OHTTP request or response over an HTTP keep-alive connection and leave the connection idle, pinning pooled or direct memory allocations across concurrent connections to induce denial of service.

Amit Schendel
Amit Schendel
2 views•8 min read
•about 5 hours ago•CVE-2026-104773
6.8

CVE-2026-104773: Session Fixation in CKAN User Registration View

A session fixation vulnerability (CWE-384) exists in CKAN (Comprehensive Knowledge Archive Network) prior to versions 2.10.11 and 2.11.6. When configured with server-side session storage and active public web registration, the user registration view programmatically authenticates newly created accounts without regenerating the active session identifier. An attacker capable of fixing or capturing a victim's pre-authentication session cookie can hijack the newly registered account immediately after registration completes.

Alon Barad
Alon Barad
2 views•9 min read