[Medium]: Patch to upgrade llhttp from v6.1.1 to v9.1.2 to address CVE-2025-23167

[durgajagadeesh]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

• Upgrading llhttp-v6 to llhttp-v9.1.2 is sufficient to resolve CVE-2025-23167. Abhilash has confirmed this, and I have included the security test results in the comments section.
• Upstream llhttp-v9.1.2 release reference: https://github.com/nodejs/llhttp/releases
  https://github.com/nodejs/llhttp/archive/refs/tags/release/v9.1.2.tar.gz

Change Log

• Modified file: nodejs18.spec
• New file: upgrade_llhttp-v6.1.1_to_llhttp-v9.1.2.patch
• New file: update_callBack_pointers_in_llhttp_settings_t_structure_fix_http_parser_error.patch

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2025-23167

Test Methodology

• Buddy Build results.
• This patch is applied cleanly.

[Kanishk-Bansal]

Buddy Build

[durgajagadeesh]

Buddy Build

Hi @Kanishk-Bansal,
The build got failed, checking for the failure reason.

-Thank you!

[durgajagadeesh]

Hi @Kanishk-Bansal and @kgodara912
I have received the security test logs from the MSRC team.
Based on these results, Abhilash has confirmed that there is no need to apply any additional CVE fix with this upgrade, as the upgraded patch already includes the CVE fix.
Please see the logs below for your reference.

This is the POC abhilash was using : CVE-2025-23167 : HTTP Parser Flaw in Node.js 20 Allows Request Smuggling

Default response without patch :

Binary with patch throws HTTP 400:

-Thank you!

[durgajagadeesh]

@kgodara912,
The patch was applied without issues and has been tested successfully on the local VM.

-Thank you!

[Kanishk-Bansal]

Buddy Build

[durgajagadeesh]

Buddy Build

Hi @Kanishk-Bansal and @kgodara912,
The Buddy Build results were passed, and my patch applied successfully as shown in below reference screenshot.

-Thank you!

[Malateshk007]

@Sumynwa. could you please share your review and signoff on this PR if all good?