HTTP Response Queue Poisoning in Node.js http.Agent
CVE-2026-48931 is a low-severity vulnerability in Node.js affecting the HTTP Agent. The issue is described as a race condition / TOCTOU flaw in the HTTP agent that can lead to HTTP response queue poisoning. In the vulnerable condition, a client may accept as valid an HTTP response that is received before the client has actually sent the corresponding request. This breaks the expected request/response sequencing assumptions in the client-side HTTP handling logic and can allow an attacker to inject or poison queued responses associated with future requests.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A low-severity Node.js HTTP agent race condition that can enable response queue poisoning.
A low-severity Node.js HTTP response queue poisoning flaw where a client may accept a response before sending the original request.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.