Back to vendor advisories
Microsoft Security Response CenterCVE-2025-23167

A flaw in Node.js 20's HTTP parser allows improper termination of HTTP/1 headers using `\r\n\rX` instead of the required `\r\n\r\n`. This inconsistency enables request smuggling, allowing attackers to bypass proxy-based access controls and submit unauthorized requests. The issue was resolved by upgrading `llhttp` to version 9, which enforces correct header termination. Impact: * This vulnerability affects only Node.js 20.x users prior to the `llhttp` v9 upgrade.

MediumVendor CVSS 6.5 / 10 1 CVE Published Sep 4, 2025 at 12:32 AM UTC

Summary

Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?

One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information.

If impact to additional products is identified, we will update the CVE to reflect this.

Products covered

  • azl3 nodejs 20.14.0-9 on Azure Linux 3.0

  • azl3 fluent-bit 3.1.9-4 on Azure Linux 3.0

  • cbl2 fluent-bit 3.0.6-2 on CBL Mariner 2.0

  • cbl2 nodejs18 18.20.3-8 on CBL Mariner 2.0

  • azl3 nodejs 20.14.0-10 on Azure Linux 3.0

  • azl3 nodejs 20.14.0-14 on Azure Linux 3.0

  • cbl2 nodejs18 18.20.3-12 on CBL Mariner 2.0

  • cbl2 nodejs18 18.20.3-12 on CBL-Mariner 2.0

Show 5 more products
  • cbl2 nodejs18 18.20.3-9 on CBL Mariner 2.0

  • cbl2 nodejs18 18.20.3-10 on CBL Mariner 2.0

  • azl3 nodejs 20.14.0-13 on Azure Linux 3.0

  • cbl2 nodejs18 18.20.3-11 on CBL Mariner 2.0

  • cbl2 nodejs18 18.20.3-12

Remediation

CBL-Mariner Releases Release Notes

CVEs in this advisory 1

Updates

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  3. Added to SecurityAlert

    We collected the advisory from the official source.

  4. Confirmed at the source

    Our collector saw this advisory during a later source check.