Migrating to Axios v1.15.2
Version v1.15.2 introduces 2 breaking changes. This guide details how to update your code.
Released: 4/21/2026
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
Node HTTP adapter`resolveConfig``mergeConfig`validator paths`socketPath``auth``baseURL``beforeRedirect``insecureHTTPParser`kAxiosSocketListenerkAxiosCurrentReqBreaking Changes
●Issue #1
The Node HTTP adapter now strictly reads only own properties and uses null-prototype config objects. Configurations for `auth`, `baseURL`, `socketPath`, `beforeRedirect`, and `insecureHTTPParser` that relied on prototype chain properties may no longer function as expected.
●Issue #2
Non-string values provided for `socketPath` will now be rejected, resulting in an `AxiosError` with code `ERR_BAD_OPTION_VALUE`.
Migration Steps
- 1If you rely on prototype properties in configuration objects like `auth` or `baseURL` when using the Node HTTP adapter, update your configuration to explicitly set these properties directly.
- 2If using Unix domain sockets via `socketPath`, ensure the value is a string. If you need to allowlist specific paths, configure the new `allowedSocketPaths` option.
Release Summary
This release focuses heavily on security, hardening the Node HTTP adapter against prototype pollution and adding controls to mitigate SSRF via Unix domain sockets, alongside fixing a critical keep-alive socket memory leak.
Need More Details?
View the full release notes and all changes for Axios v1.15.2.
View Full Changelog