Axios release notes, breaking changes, and upgrade notes.
Promise based HTTP client for the browser and Node.js StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
Axios v0.35.0 tightens parameter validation and changes form serialization behavior, with stricter handling of deeply nested parameters and native proxy-agent configurations. It also fixes connection-pool handling, upload limits, FileList conversion, and browser/runtime compatibility across Node and browser environments.
affected
Users relying on deeply nested `params`, prior sparse-array or numeric-index form serialization, or custom agents overriding native proxy lifecycle hooks may see changed behavior or validation errors.
action
Review parameter depth, form serialization expectations, and custom native-proxy agent configurations before upgrading.
release_signals
-Parameters nested deeper than 100 levels now reject with ERR_BAD_OPTION_VALUE.
-Sparse arrays and non-canonical numeric form indexes such as `01` now serialize as keyed objects rather than being collapsed into arrays.
-On runtimes with native environment proxy support, agents overriding native pool-management or TLS-session lifecycle hooks now reject with ERR_BAD_OPTION_VALUE; use an agent constructed without `proxyEnv` for these configurations.
migration_steps1 steps
01For agent configurations that override native pool-management or TLS-session lifecycle hooks on runtimes with native environment proxy support, construct the agent without `proxyEnv`.
Axios 1.21.0 adds response-duration reporting and opt-in UTF-8 Basic authentication, alongside broad fixes to runtime compatibility, adapters, headers, and diagnostics. It also changes how header defaults are recognized: custom class instances are no longer treated as method-specific defaults unless converted to a plain map or compatible AxiosHeaders instance.
affected
Axios users relying on custom class instances for header defaults may need to convert them; users needing Unicode Basic authentication can opt in, while other users benefit from timing and compatibility fixes.
action
Review header-default configuration for custom class instances and convert any such defaults to plain maps or compatible AxiosHeaders instances.
release_signals
-Only plain objects, null-prototype maps, and compatible `AxiosHeaders` instances are treated as common or method-specific header defaults. Custom class instances may instead be interpreted as literal header values, including for requests using other methods.
v0.34.0highbreakingfeaturesecuritySep 13, 2026
v0.34.0
This release hardens request configuration and proxy handling, adds caller diagnostics and cancellation context, and tightens TypeScript header types.
affected
Users relying on Promises, functions, or custom objects as header values, or using NO_PROXY with CIDR ranges, will need to update their code.
action
Review and update header value assignments and NO_PROXY configurations to comply with the new TypeScript header type restrictions and CIDR range support.
release_signals
-TypeScript now rejects header values that are Promises, functions, or objects with custom toString() methods. Resolve promises, call functions, or explicitly convert objects before assigning header values.
This release introduces RFC 9110 status-code aliases, hardens runtime option handling against security vulnerabilities, and improves reliability in Node.js and XHR. It also includes various bug fixes and dependency updates.
affected
Users relying on the deprecated HTTP status code names (PayloadTooLarge, UnprocessableEntity) or custom error handling may need to update their code.
action
Update to v1.20.0 to benefit from security fixes and new features, and replace deprecated status code names with their new aliases.
release_signals
-HTTP Status Naming: Added ContentTooLarge (413) and UnprocessableContent (422), while retaining PayloadTooLarge and UnprocessableEntity as backward-compatible deprecated aliases.
v1.16.1highbreakingsecurityMay 13, 2026
v1.16.1
This release includes a defence-in-depth fix for prototype pollution in `formDataToJSON`, hardens proxy and CI workflows, restores Webpack 4 compatibility for the fetch adapter, and includes several small bug fixes and maintenance improvements.
affected
Users relying on passing `URL` objects as `config.url` will need to revert to string URLs until the feature is reintroduced.
action
Update to v1.16.1 to benefit from security fixes and bug improvements, and revert to string URLs if using `URL` objects as `config.url`.
release_signals
-Reverted support for passing a `URL` object as `config.url` due to regressions; this support will be reintroduced in a later release once the underlying issues are addressed.
!Hardened `formDataToJSON` against already-polluted `Object.prototype` by walking own properties only, so attacker-controlled keys inherited from a poisoned prototype cannot propagate through deserialization.
This release backports security and hardening fixes from the v1.x branch into v0.x, including prototype-pollution protections, default error redaction, stricter proxy/cookie/socket handling, and a breaking change to merged config and header object prototypes.
affected
Users relying on implicit string coercion against merged config or header objects will be affected.
action
Update code to use Object.prototype.hasOwnProperty.call(obj, key) for merged config or header objects.
release_signals
-mergeConfig and header merging now return objects with a null prototype to block prototype-pollution gadgets. Consumers must use Object.prototype.hasOwnProperty.call(obj, key) and avoid implicit string coercion against merged config or header objects.
This release introduces support for the QUERY HTTP method and a new `ECONNREFUSED` error constant, along with significant bug fixes for HTTP, fetch, and XHR adapters related to redirects, aborts, headers, and timeouts.
affected
Users relying on `maxBodyLength` and `maxContentLength` in the fetch adapter, or those using percent-encoded credentials in URLs, will be affected.
action
Review the changes related to `maxBodyLength`, `maxContentLength`, and URL-decoded credentials before upgrading.
release_signals
-Fetch adapter now enforces `maxBodyLength` and `maxContentLength`, which were previously ignored.
-
+Adds `response.duration` in milliseconds, including on `error.response` when available; it measures adapter execution and replaces any `duration` value supplied by a custom adapter.
+Adds opt-in Unicode Basic authentication for XHR and Fetch through `transitional.encodeBasicAuthUsername: true`.
migration_steps2 steps
01Convert custom class instances used as header defaults to plain maps (for example, `{ post: { ...customDefaults } }`) or compatible `AxiosHeaders` instances.
02For Unicode Basic authentication, enable `transitional.encodeBasicAuthUsername: true`, provide the original Unicode username, and remove manual pre-encoding workarounds.
NO_PROXY / no_proxy entries now support IPv4 and IPv6 CIDR ranges. Previously ineffective ranges now cause matching IP destinations to bypass the proxy; review existing ranges when upgrading.
!Prevent inherited properties from influencing form serializer options, default request methods, headers on interceptor-returned configs, and HTTP redirect hooks.
!Replace quadratic regular-expression backtracking in proxy bypass hostname normalization with a linear scan, preventing excessive processing of crafted redirect hostnames.
+Caller Diagnostics: Enable captureCallerStack: true on a request or instance to append original caller frames to asynchronous error stacks.
+Cancellation Context: Preserve AbortSignal.reason as CanceledError.reason, including objects and falsy values.