Vulnerability · CVE-2026-105481
A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request.
Published Oct 22, 2026 · catalog updated Oct 24, 2026 · A flaw in Node.js
Last checked Nov 4, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-105481. EPSS is 0.32%. Act only if a listed version of A flaw in Node.js is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (A flaw in Node.js).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium6.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.32%
- Remediation
- Advisory link
- Affected products
- Alpine:v3.21 nodejs · Alpine:v3.22 nodejs · Alpine:v3.23 nodejs · Alpine:v3.24 nodejs · Debian:12 nodejs · Debian:13 nodejs
A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request. This is an incomplete fix of CVE-2026-48931. The guard that destroys idle keep-alive sockets when unexpected data arrives only runs when the event loop polls for I/O. If an unsolicited response has already reached the socket but has not been read yet when the socket is handed to a new request, for example because the event loop was busy with synchronous work, the guard is removed without seeing it and the data is parsed as the response to the new request. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Alpine:v3.21 nodejs0 → 22.23.4-r0
- Alpine:v3.22 nodejs0 → 22.23.4-r0
- Alpine:v3.23 nodejs0 → 24.22.1-r0
- Alpine:v3.24 nodejs0 → 24.22.1-r0
- Debian:12 nodejs18.13.0+dfsg1-1, 18.13.0+dfsg1-1.1, 18.19.0+dfsg-1
- Debian:13 nodejs20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2
- Debian:14 nodejs20.19.2+dfsg-1, 20.19.4+dfsg-1, 20.19.5+dfsg+~cs20.19.12-1
How to fix CVE-2026-105481
Upgrade
CVE-2026-105481 lists a fix boundary at 22.23.4-r0. Compare the installed build with that boundary before you change production.
Version check
Fixed in 22.23.4-r0 · 9 other ranges on the advisory
Advisory
Open the bsi record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-105481. EPSS is 0.32%. Act only if a listed version of A flaw in Node.js is installed.
Which versions are affected?
Compare what you have installed with 0 → 22.23.4-r0, 0 → 24.22.1-r0, 18.13.0+dfsg1-1, 18.13.0+dfsg1-1.1, 18.19.0+dfsg-1, 20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2, 20.19.2+dfsg-1, 20.19.4+dfsg-1, 20.19.5+dfsg+~cs20.19.12-1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.32%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Oct 22, 2026 · Trivy Vulnerability DB
Detected
Oct 22, 2026 · Trivy Vulnerability DB
Updated
The description or metadata changed.
Oct 24, 2026 · Trivy Vulnerability DB
Fix available
nodejs fixed in 22.23.4-r0; nodejs fixed in 22.23.4-r0; nodejs fixed in 24.22.1-r0; nodejs fixed in 24.22.1-r0
Oct 24, 2026 · Trivy Vulnerability DB
Fix available
nodejs fixed in 22.23.4-r0
Oct 24, 2026 · Trivy Vulnerability DB
Fix available
nodejs fixed in 24.22.1-r0
Oct 24, 2026 · Trivy Vulnerability DB
Updated
A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request. This is an incomplete fix of CVE-2026-48931. The guard that destroys idle keep-alive sockets when unexpected data arrives only runs when the event loop polls for I/O. If an unsolicited response has already reached the socket but has not been read yet
Sources
- BSI CERT-BundGovernment advisoryCVE-2026-105481
Node.js: Mehrere Schwachstellen
wid.cert-bund.de - CVE.orgVulnerability recordCVE-2026-105481
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-105481
30-day exploitation probability 0.32%
first.org - Trivy Vulnerability DBPackage advisoryALPINE-CVE-2026-105481
A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request. This is an incomplete fix of CVE-2026-48931. The guard that destroys idle keep-alive sockets when unexpected data arrives only runs
osv.dev - Trivy Vulnerability DBPackage advisoryDEBIAN-CVE-2026-105481osv.dev
References
Freshness
Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- BSI CERT-BundNov 4, 2026
- FIRST EPSSNov 4, 2026
- Trivy Vulnerability DBOct 25, 2026
- CVE.orgOct 23, 2026
- Trivy Vulnerability DBOct 23, 2026