Bump axios from 1.15.0 to 1.16.0#1468
Conversation
Bumps [axios](https://github.com/axios/axios) from 1.15.0 to 1.16.0. - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](axios/axios@v1.15.0...v1.16.0) --- updated-dependencies: - dependency-name: axios dependency-version: 1.16.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Stale comment
No blocking issues found in this dependency bump.
Security
- This is a net security improvement.
axios@1.15.0is inside multiple affected ranges published on 2026-04-24 and patched by>=1.15.1/>=1.15.2, includingGHSA-pmwg-cvhr-8vh7/CVE-2026-42043(incompleteNO_PROXYfix),GHSA-q8qp-cvcw-x6jj/CVE-2026-42264(prototype-pollution gadgets in the HTTP adapter), andGHSA-3w6x-2g7m-8v23/CVE-2026-42044(prototype-pollution gadget inparseReviver). Several additional moderate advisories also list<=1.15.0as affected.- Moving to
axios@1.16.0gets the PR onto a patched line and also picks up the 1.16.0 adapter bug fixes around redirects, abort handling, timeouts, and header handling.- Supply-chain delta is small: the PR only changes
package.jsonandyarn.lock, introduces no new packages, and the only transitive metadata change is the declaredfollow-redirectsrange. The lockedfollow-redirectsversion remains1.16.0.Safety of merging
- In this repo,
axiosis only imported insrc/utils/apiCallHandler.js, where it is used as plainget/post/put/deletehelpers.- I found no usage of the higher-risk axios options touched by the recent advisories or 1.16.0 behavior changes: no
baseURL,validateStatus,withXSRFToken,paramsSerializer,beforeRedirect,proxy,responseType: 'stream',maxContentLength, ormaxBodyLengthusage insrc/.- The main 1.16.0 observable changes are fetch-adapter limit enforcement, proxy
Hostheader preservation, URL-decoding of basic-auth credentials in URLs, stricter protocol parsing, and UTF-8 encoding fixes. None of those appear to be exercised by this codebase's current axios usage.Local verification
yarn lint✅CI=true yarn test✅ (92suites /820tests passed)yarn start✅ (webpack compiled successfully)yarn exec cypress runcould not be completed locally because the Cypress binary was not present in the machine cache, and an attemptedcypress installdid not produce a usable binary in this environment.Recommendation
- Merge with caution: the version bump improves security and looks low-risk for this repository's axios usage, but I would still wait for the PR's
test-cypressGitHub check to pass before merging, since local end-to-end coverage was not available here.Sent by Cursor Automation: Editor-UI - Tests Dependabot PRs
There was a problem hiding this comment.
No blocking issues found in this dependency bump.
Security
- This update improves the security posture compared with
axios 1.15.0. - GitHub advisory data shows
axios 1.15.0is still inside several affected ranges that were only patched in1.15.1/1.15.2, including high-severity prototype-pollution gadgets leading to header injection / request hijacking (GHSA-6chq-wfr3-2hj9,GHSA-pf86-5x62-jrwf), the incompleteNO_PROXYfix specific to1.15.0(GHSA-pmwg-cvhr-8vh7), and additional moderate issues such as XSRF token leakage and JSON response tampering (GHSA-xx6v-rp6x-q39c,GHSA-3w6x-2g7m-8v23). - The transitive update to
follow-redirects 1.16.0also fixesCVE-2026-40895, where custom auth-style headers could be forwarded across cross-domain redirects in Node. - I did not find a known advisory that newly affects
axios 1.16.0.
Safety Of Merging
- Scope is minimal: only
package.jsonandyarn.lockchange. - In this repository, runtime usage is limited to
src/utils/apiCallHandler.js, which uses plainaxios.get/post/put/deletecalls withheadersandwithCredentials. - I found no local use of the higher-risk axios features touched by
1.16.0's notable behavior changes, such asaxios.create,proxy,maxRedirects,maxBodyLength,maxContentLength, customHostheaders, URL-embedded basic auth,withXSRFToken,validateStatus, orparseReviver. - Upstream
1.16.0changes are mostly around Node/fetch adapter redirects, abort cleanup, proxy/header handling, timeout handling, and stricter protocol parsing, so regression risk for this browser-focused app looks low.
Test Results
yarn install --immutable✅yarn lint✅CI=true yarn run test --coverage --maxWorkers=4 --workerThreads=true --reporters=default --reporters=jest-junit --reporters=jest-github-actions-reporter✅ (92suites,820tests)yarn exec cypress run --config-file cypress.config.mjs --browser chromecould not be completed here because the Cypress binary was not installed in the agent and downloading it fromdownload.cypress.iofailed in this environment (OpenSSL SSL_connect: SSL_ERROR_SYSCALL). That looks like an environment egress limitation rather than a regression from this PR.
Recommendation
Merge with caution. I do not see a code-level reason to hold this update, and it resolves known issues present in axios 1.15.0. The only caution is that I could not run Cypress locally in this cloud environment, so I would rely on normal CI/e2e coverage or rerun e2e in an environment that can download the Cypress binary if you want full end-to-end validation before merging.
Sent by Cursor Automation: Editor-UI - Tests Dependabot PRs
|
@dependabot rebase |
|
Looks like axios is up-to-date now, so this is no longer needed. |


Bumps axios from 1.15.0 to 1.16.0.
Release notes
Sourced from axios's releases.
... (truncated)
Changelog
Sourced from axios's changelog.
... (truncated)
Commits
df53d7dchore(release): prepare release 1.16.0 (#10834)9d92bcdfix: gadgets and smaller issues (#10833)5107ee6fix: prevent undefined error codes in settle (#7276)e573499fix(fetch): defer global access in fetch adapter (#7260)ad68e1afix(http): honor timeout during connect without redirects (#10819)2a51828fix(http): decode URL basic auth credentials (#10825)0e8b6bbfix(http): preserve user-supplied Host header when forwarding through a proxy...79f39e1docs: document paramsSerializer.encode for strict RFC 3986 query encoding (#1...0fe3a5f[Docs/Types] UpdateparseReviverTypeScript definitions for ES2023 and add ...cd6737fchore: matches the sibling responseStream.on(aborted) handler and added tests...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)