CVE-2026-101905: Axios: Node HTTP adapter prototype-pollution gadget allows request socket hijack via inherited createConnection

Published Sep 28, 2026
·
Updated

Axios is a promise-based HTTP client for the browser and Node.js. From 1.15.2 until 1.20.0, the Node HTTP adapter in lib/adapters/http.js supplies request options without an own createConnection value. A separate same-process prototype-pollution flaw places a function on Object.prototype.createConnection. Node resolves and invokes the inherited createConnection socket factory, allowing the attacker-controlled function to select the transport endpoint. The attacker endpoint can receive request headers and bodies, including credentials, and return attacker-controlled responses while the URL appears legitimate. This issue is fixed in version 1.20.0.

Affected Software

1 affected component
npm/axios>=1.15.2<1.20.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Axios to a version that resolves this vulnerability.

    Fixed in 1.20.0

Event History

Sep 28, 2026
CVE Published
via MITRE·05:31 PM
Data Sourced
via MITRE·05:31 PM
DescriptionWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed in practice?

Exposure is limited to Axios use through its Node HTTP adapter. An affected process must also have a separate same-process prototype-pollution condition that can place a function on Object.prototype.createConnection.

2

What capability does an attacker need before this can be exploited?

The attacker needs a way to trigger prototype pollution in the same Node.js process and assign an attacker-controlled function to Object.prototype.createConnection. Without that prerequisite, the inherited socket-factory path described here is not available.

3

How can I determine whether an application may already be at risk?

Check whether the application uses Axios versions from 1.15.2 up to, but not including, 1.20.0 through the Node HTTP adapter. Also investigate whether any dependency or application input path can pollute Object.prototype, particularly with a createConnection property.

4

What should be done if an immediate Axios upgrade is not possible?

Prioritize eliminating or blocking the separate prototype-pollution condition in the same process, since it is required for exploitation. Ensure Object.prototype cannot acquire an attacker-controlled createConnection function, then upgrade Axios to 1.20.0 when possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203