# CVE-2019-15605: Other in Node > Attackers can exploit HTTP request smuggling in Node.js to deliver malicious payloads via malformed transfer-encoding headers. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Feb 2020 - **Updated:** 30 Apr 2025 - **Also known as:** ALPINE-CVE-2019-15605, CLEANSTART-2026-EW03661, CLEANSTART-2026-YO77738, DEBIAN-CVE-2019-15605, GHSA-rv6p-2q56-m955, MGASA-2020-0131, RHSA-2020:0703, RHSA-2020:0707, RHSA-2020:0708, RHSA-2020:1510, UBUNTU-CVE-2019-15605 ## What is CVE-2019-15605? CVE-2019-15605 is a critical vulnerability in Debian Debian Linux, published on 7 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests) ## Which versions are affected by CVE-2019-15605? It affects 13 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `http-parser` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser` | Red Hat:enterprise_linux:7::server | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.7.1-8.el7_7.2 | | `http-parser` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.8.0-5.el8_1.2 | | `http-parser-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.8.0-5.el8_1.2 | | `http-parser-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.8.0-5.el8_1.2 | | `http-parser` | Red Hat:rhel_e4s:8.0::appstream | All versions | 0:2.8.0-2.el8_0.2 | | `http-parser-debuginfo` | Red Hat:rhel_e4s:8.0::appstream | All versions | 0:2.8.0-2.el8_0.2 | | `http-parser-debugsource` | Red Hat:rhel_e4s:8.0::appstream | All versions | 0:2.8.0-2.el8_0.2 | | `http-parser` | Red Hat:rhel_eus:7.6::computenode | All versions | 0:2.7.1-5.el7_6.1 | | `http-parser-debuginfo` | Red Hat:rhel_eus:7.6::computenode | All versions | 0:2.7.1-5.el7_6.1 | | `http-parser-devel` | Red Hat:rhel_eus:7.6::computenode | All versions | 0:2.7.1-5.el7_6.1 | | `http-parser` | Red Hat:rhel_eus:7.6::server | All versions | 0:2.7.1-5.el7_6.1 | | `http-parser-debuginfo` | Red Hat:rhel_eus:7.6::server | All versions | 0:2.7.1-5.el7_6.1 | | `http-parser-devel` | Red Hat:rhel_eus:7.6::server | All versions | 0:2.7.1-5.el7_6.1 | Products: Debian Debian Linux, Fedoraproject Fedora, Nodejs Node.js, Opensuse Leap, Oracle Graalvm, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Redhat Software Collections. ## How do I fix CVE-2019-15605? Upgrade to a fixed version. ## Is CVE-2019-15605 being exploited? There is no known exploitation of CVE-2019-15605 in the wild and no public exploit code. Public exploit code: - PoC of Backend HTTP Socket Poisoning, via HTTP Smuggling, presented in CVE-2019-15605 (github_poc): https://github.com/0-9194/node-poc-http-smuggling ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-15605 and fix it if it is affected. What it is: CVE-2019-15605 is a critical vulnerability in Debian Debian Linux, published on 7 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-15605 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-15605/ (Markdown: https://insights.sbomify.com/CVE-2019-15605/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-15605 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-15605 - OSV: https://osv.dev/vulnerability/CVE-2019-15605 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-15605/ Summaries are generated and may contain mistakes; the official description above is the record.