A flaw in Node.js HTTP Agent can cause a client to accept as valid a response that is send before the client has sent the request.
A flaw in Node.js HTTP Agent can cause a client to accept as valid a response that is send before the client has sent the request. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
- Published
- Jun 22, 2026
- Updated
- Jul 3, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-367
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
14
Monitor
Low priority for now.
- CVSS
- 14 / 40 · 3.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 3.7
- CNA · hackerone
- 3.7
- agree
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.js22.22.3
- nodejs node.js24.16.0
- nodejs node.js26.3.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
nodejs node
- 22.22.3 and later · up to and including 22.22.3affected · semver
- 24.16.0 and later · up to and including 24.16.0affected · semver
- 26.3.0 and later · up to and including 26.3.0affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | nodejs | before 22.23.0-r0 | 22.23.0-r0 |
| Alpine:v3.23 | nodejs | before 24.17.0-r0 | 24.17.0-r0 |
| Debian:12 | nodejs | all versions | — |
| Debian:13 | nodejs | before 20.19.2+dfsg-1+deb13u3 | 20.19.2+dfsg-1+deb13u3 |
| Debian:14 | nodejs | before 24.17.0+dfsg+~cs24.13.2-1 | 24.17.0+dfsg+~cs24.13.2-1 |
| openSUSE:Leap 16.0 | nodejs22 | before 22.23.0-160000.1.1 | 22.23.0-160000.1.1 |
| openSUSE:Leap 16.0 | nodejs24 | before 24.18.0-160000.1.1 | 24.18.0-160000.1.1 |
| openSUSE:Tumbleweed | nodejs24 | before 24.17.0-1.1 | 24.17.0-1.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | nodejs16 | before 16.20.2-150400.3.42.1 | 16.20.2-150400.3.42.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | nodejs20 | before 20.20.2-150500.11.30.1 | 20.20.2-150500.11.30.1 |
| SUSE:Linux Enterprise Module for Web and Scripting 15 SP7 | nodejs22 | before 22.23.0-150700.3.12.1 | 22.23.0-150700.3.12.1 |
| SUSE:Linux Enterprise Module for Web and Scripting 15 SP7 | nodejs24 | before 24.17.0-150700.15.11.1 | 24.17.0-150700.15.11.1 |
| SUSE:Linux Enterprise Server 15 SP6-LTSS | nodejs20 | before 20.20.2-150600.3.21.1 | 20.20.2-150600.3.21.1 |
| SUSE:Linux Enterprise Server 15 SP6-LTSS | nodejs22 | before 22.23.0-150600.13.18.1 | 22.23.0-150600.13.18.1 |
| SUSE:Linux Enterprise Server 16.0 | nodejs22 | before 22.23.0-160000.1.1 | 22.23.0-160000.1.1 |
| SUSE:Linux Enterprise Server 16.0 | nodejs24 | before 24.18.0-160000.1.1 | 24.18.0-160000.1.1 |
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed56Plan
- CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 52Plan
- CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c50Plan
- CVE-2021-22931Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application crashes due to missing input validation46Plan
- CVE-2020-8277A Node.js application that allows an attacker to trigger a DNS request for a host of their choice could trigger a Denial of Service in versi46Plan
- CVE-2017-14849Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was incompatible with the p46Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:nodejs | 22.23.0-r0 · Alpine:v3.21 | Package registry (OSV) |
| debian:nodejs | 20.19.2+dfsg-1+deb13u3 · Debian:13 | Package registry (OSV) |
| opensuse:nodejs22 | 22.23.0-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:nodejs24 | 24.17.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:nodejs16 | 16.20.2-150400.3.42.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:nodejs20 | 20.20.2-150600.3.21.1 · SUSE:Linux Enterprise Server 15 SP6-LTSS | Package registry (OSV) |
| suse:nodejs22 | 22.23.0-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:nodejs24 | 24.18.0-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- nodejs.org/en/blog/vulnerability/june-2026-security-releases
- www.openwall.com/lists/oss-security/2026/07/02/2
- jdstaerk.substack.com/p/nodejs-security-fix-silently-broke
Vendor advisories and official records. Exploit/PoC links are deliberately left out.