vulns.co
/
GKData.io MCP and API Buy me a coffee

Microsoft · Injection and untrusted input

Kestrel HTTP framing differed across proxy and application boundaries

Kestrel and an upstream proxy could disagree about where one HTTP request ended and another began. This could bypass security checks in affected deployments, but the consequences depended on the full proxy and application setup. The researcher reports a USD 10,000 award.

Read the original writeupUSD 10,000 reported award · Reviewed 2026-10-02

Root cause

Kestrel accepted malformed HTTP/1.1 chunk metadata that an upstream proxy could interpret differently. The two parsers could then disagree about where one request ended and the next began.

Demonstrated impact

Security controls could be bypassed in affected deployments. Consequences depended on the complete proxy/application architecture, not merely the presence of Kestrel.

What to check for

  • Define consistent message-boundary contracts across intermediaries and application servers; reject ambiguous framing.
  • Apply the vendor updates to deployed runtimes. Microsoft also requires affected self-contained applications to be rebuilt and redeployed with the corrected runtime.

Award and evidence

USD 10,000Bug Bounty · Researcher Reported
How the award was verified, and what the record does not establish

Exact award comes from the researcher. The July 31, 2025 official program announcement supplies USD context only; its later award-table changes do not establish this amount. Payment completion is unverified.

  • The award and its date are researcher-reported, not independently vendor-confirmed.
  • Impact varies with deployment architecture; generic consequences are not evidence of actual victim compromise.
  • Dollar notation is interpreted through official program currency context; no conversion is used.

Timeline

Published
2025-11-07explicit · Detailed article date; vendor disclosure preceded it.
Public Disclosure
2025-10-14explicit
Reported
2025-06-22explicit
Awarded
2025-07-21explicit
Fixed
2025-10-14explicit · Public patch release; vendor advisory independently identifies patched versions.

Related cases

All 4 cases in Injection and untrusted input

Sources

  1. ASP.NET Core CVE-2025-55315 disclosure and award timelineSiddhant Kalgutkar / Praetorian · reviewed 2026-10-02
  2. Microsoft Security Advisory CVE-2025-55315Microsoft .NET security team · reviewed 2026-10-02
  3. .NET Bounty Program update, July 31, 2025Madeline Eckert and Barry Dorrans / Microsoft · reviewed 2026-10-02

Record reviewed 2026-10-02. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software