CVE-2018-12116
No exploitation reported by the sources we read.
- Published2018-11-28
- Fixed in8.14.0 · 6.15.0
- WeaknessCWE-115
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2018-11-2817:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-12116?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-12116?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.x | ≥ 8.9.0, < 8.14.0 | 8.14.0 | NVD |
| 6.x | ≥ 6.9.0, < 6.15.0 | 6.15.0 | NVD |
| 6.x | ≥ 6.0.0, ≤ 6.8.1 | no fix published | NVD |
| 8.x | ≥ 8.0.0, ≤ 8.8.1 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 12.x | = 12 | no fix published | NVD |
| 15.x | = 15 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.x | = 7 | no fix published | NVD |
| 8.x | = 8 | no fix published | NVD |
1 more product in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Node.js to 8.14.0 · 6.15.0
Advisories and patches
- nodejs.orgPatch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Published
- 2018-11-28
- Last Modified
- 2026-10-08
- NVD status
- Modified
Frequently asked questions
What is CVE-2018-12116?
Is CVE-2018-12116 actively exploited?
What is the CVSS score for CVE-2018-12116?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.