AXIOS · CVE-2026-101901 · Package
FIX → 1.20.0 · >=1.20.0
When axios uses HTTP/2 in Node.js, a failed or malicious HTTP/2 session emits an error that axios does not handle, which throws an uncaught exception. An attacker who can influence the request destination or run that server can crash the calling Node.js process.
first public Sep 16, 2026 · 3 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only applications that run axios in Node.js with HTTP/2 enabled (httpVersion: 2) and send requests to destinations an attacker can influence or operate. Default HTTP/1.1 usage, browser builds, and applications that do not enable axios HTTP/2 support are not affected.
Not affected if browser-only, default-config, http1-only
Who cares axios, http2, node.js, npm
npm ls axioshttpVersion: 2 or http2Options in axios configuration; without them the flaw is not reachedUpgrade to 1.20.0 · >=1.20.0
Axios versions with Node.js HTTP/2 support can terminate the caller’s process when a ClientHttp2Session emits an error event that is not handled by axios.
This affects applications that use the Node HTTP adapter with httpVersion: 2. A malicious, unavailable, or non-HTTP/2 endpoint can cause an uncaught exception instead of a normal rejected axios request.
The impact is denial of service. In affected applications, an attacker who can influence the request destination, or operate the destination server, may be able to crash the Node.js process.
This does not affect default HTTP/1.1 usage, browser XHR/fetch adapters, or applications that do not enable axios HTTP/2 support.
Affected path:
Caller-controlled http2Options can make the issue easier to trigger, but passing arbitrary attacker input into axios config is caller-controlled behavior and should not be the primary advisory framing.
Http2Sessions.getSession() creates a session with http2.connect(authority, options) but only registers a close handler. It does not register an error handler on the returned ClientHttp2Session.
When the session emits error, Node treats it as an unhandled EventEmitter error and throws. This can bypass the normal axios Promise rejection path and terminate the process.
axios ;
axios.(, {
: ,
:
});
<details>
<summary><h3>Original report</h3></summary>
</details>Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
1.20.0 or later (affected from 1.13.0)Expected vulnerable behavior: the process exits with an uncaught ECONNREFUSED session error instead of only rejecting the axios request.
Disable axios HTTP/2 for untrusted or user-influenced destinations and use the default HTTP/1.1 adapter until a fixed release is available. Also avoid passing attacker-controlled values into http2Options; axios config is trusted application input.
Hi, i'm RelunSec a security researcher working with InsiteTech.jp
i want let you known, i finded a DoS in axios, to reproduce that, that is the example of a server
const http = require('http');
// Import the local axios version to ensure the patch is active
const axios = require('../../lib/axios.js').default;
const url = require('url');
// A public HTTP/2 server to make internal requests to.
// This simulates an external service your application might interact with over HTTP/2.
const TARGET_URL = 'https://nghttp2.org/';
const PORT = 3000;
const server = http.createServer(async (req, res) => {
const parsedUrl = url.parse(req.url, true);
const http2optionId = parsedUrl.query.http2optionId;
if (!http2optionId) {
console.warn(`[SERVER] Rejected request: Missing http2optionId parameter`);
res.writeHead(400, { 'Content-Type': 'text/plain' });
res.end('Error: Missing http2optionId query parameter. Usage: ?http2optionId=value\n');
return;
}
console.log(`[SERVER] Received request with http2optionId: ${http2optionId}`);
// Create an Axios instance configured for HTTP/2
// The 'id' in http2Options makes each session configuration unique.
const axiosInstance = axios.create({
baseURL: TARGET_URL,
httpVersion: 2,
http2Options: {
// rejectUnauthorized: false, // Uncomment if targeting a local HTTP/2 server with self-signed cert
id: http2optionId, // This is the attacker-controlled unique part
},
// Adding a short timeout to prevent attacker from waiting too long if target is slow
timeout: 5000
});
try {
const response = await axiosInstance.get('/');
res.writeHead(200, { 'Content-Type': 'text/plain' });
res.end(`Internal HTTP/2 request successful for ID: ${http2optionId}\nStatus: ${response.status}`);
} catch (error) {
// Check for the specific error indicating session limit reached
if (error.isAxiosError && error.code === axios.AxiosError.ERR_BAD_OPTION_VALUE) {
console.error(`[SERVER] Internal HTTP/2 request failed for ID: ${http2optionId}: ${error.message}`);
res.writeHead(500, { 'Content-Type': 'text/plain' });
res.end(`Internal HTTP/2 request failed for ID: ${http2optionId}: ${error.message}`);
} else {
console.error(`[SERVER] Internal HTTP/2 request failed for ID: ${http2optionId}:`, error.message);
res.writeHead(500, { 'Content-Type': 'text/plain' });
res.end(`Internal HTTP/2 request failed for ID: ${http2optionId}: Generic error - ${error.message}`);
}
}
});
server.listen(PORT, () => {
console.log(`PoC Server listening on http://localhost:${PORT}`);
console.log(`Targeting internal HTTP/2 requests to: ${TARGET_URL}`);
console.log(`Send requests to http://localhost:${PORT}?http2optionId=...`);
console.log(`Expected behavior with current patch: After ~100 unique http2optionIds, subsequent requests will receive ERR_BAD_OPTION_VALUE.`);
});
i tested all that in latest git version, after starting the server.cjs, to trigger that you just need do
relunsec@relunsec:~/software/axios-1/poc/poc$ curl http://127.0.0.1:3000/?http2optionId=hi
curl: (52) Empty reply from server
that is extremly simple to trigger
it confirms a DoS in the HTTP/2 session cache, that needs be patched, the impact is will lead the server crashes and shutdown by an attacker, the server is written properly and no flaws in it and try catch blocks and errors handled however because that is an axios internal error will crash
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.