# 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.


- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** ALPINE-CVE-2026-105481, AZL-111056, BIT-node-2026-105481, BIT-node-min-2026-105481, DEBIAN-CVE-2026-105481, GHSA-7h83-3rfm-3p3v, UBUNTU-CVE-2026-105481

## What is CVE-2026-105481?

CVE-2026-105481 is a medium-severity vulnerability in nodejs node, published on 23 Oct 2026. 

### Official description

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**.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2026-105481?

2 open source packages ship an affected version, including node and node-min.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | All versions | 22.23.4, 24.22.1, 26.12.1 |
| `node-min` | Bitnami | All versions | 22.23.4, 24.22.1, 26.12.1 |

## How do I fix CVE-2026-105481?

Upgrade node to a fixed version for your release line: 22.23.4, 24.22.1 or 26.12.1.

## Is CVE-2026-105481 being exploited?

There is no known exploitation of CVE-2026-105481 in the wild and no public exploit code.

Public exploit code:

- Offline Node.js evidence checker for CVE-2026-105481: HTTP keep-alive premature-response acceptance. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. (github_poc): https://github.com/CompleteTech-Security/node-cve-2026-105481-check

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105481 and fix it if it is affected.

What it is: CVE-2026-105481 is a medium-severity vulnerability in nodejs node, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-105481 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected all versions; fixed in 22.23.4, 24.22.1, 26.12.1
- node-min (Bitnami): affected all versions; fixed in 22.23.4, 24.22.1, 26.12.1

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-2026-105481/ (Markdown: https://insights.sbomify.com/CVE-2026-105481/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105481
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105481
- OSV: https://osv.dev/vulnerability/CVE-2026-105481

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105481/
Summaries are generated and may contain mistakes; the official description above is the record.