Quick answers
- Is CVE-2026-105481 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105481 being exploited in the wild.
- How severe is CVE-2026-105481?
- Medium severity, with a CVSS score of 6.5, published 23 October 2026.
- Which products and versions are affected?
- OpenJS Foundation Node.js 22.x, 24.x, 26.x.
- Is there a fix for CVE-2026-105481?
- Yes: fixed in Node.js v22.23.4, v24.22.1, v26.12.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105481 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105481?
- Check whether you run OpenJS Foundation Node.js at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Node.js v22.23.4, v24.22.1, v26.12.1
Technical details
The HTTP Agent in Node.js reuses keep-alive sockets for multiple requests, but a guard that clears unexpected data only runs during event loop I/O polling. If an unsolicited response has arrived on a socket but not yet been read when that socket is reused for a new request—because the event loop was busy with synchronous work—the guard is never triggered and the stale response data is parsed as the current request's response. This incomplete fix of CVE-2026-48931 is a logic error in the connection reuse mechanism that affects the HTTP/HTTPS Agent.
Affected products
- OpenJS Foundation Node.js 22.x, 24.x, 26.x
Timeline
- 2026-10-21: disclosed
- 2026-10-23: advisory