# axios/release
Axios v0.32.0
importance: criticalbreakingmigrationfeaturesecurity
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.
!Default error redaction to prevent credential leaks in logs
!Cookie & XSRF handling improvements
!Proxy bypass IPv6 parity fixes
!Node http adapter hardening with stricter Proxy-Authorization and socketPath handling
!Browser xhr adapter stricter own-property checks
+Default error redaction in AxiosError.toJSON()
+Stricter proxy bypass IPv6 parity handling
+Node http adapter hardening with allowedSocketPaths allowlist
migration_steps1 steps
- 01Use Object.prototype.hasOwnProperty.call(obj, key) for merged config or header objects to avoid implicit string coercion.
code_snippet
Object.prototype.hasOwnProperty.call(obj, key)# community_signal
How useful is this release to your stack?
—
net score
Sign in with GitHub to cast your vote.
Sign in with GitHub to vote
You’ll return to this release, then choose your vote.