fix(deps): upgrade axios to 1.15.0 to fix CVE-2025-62718#466
Merged
cameri merged 1 commit intocameri:mainfrom Apr 18, 2026
Merged
fix(deps): upgrade axios to 1.15.0 to fix CVE-2025-62718#466cameri merged 1 commit intocameri:mainfrom
cameri merged 1 commit intocameri:mainfrom
Conversation
Contributor
Author
|
HI @cameri, when you have time please review this PR |
This was referenced Apr 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Axios Upgrade to fix CVE-2025-62718
Description
This PR upgrades the Axios dependency to version ^1.15.0 to address the critical security vulnerability CVE-2025-62718.
Versions of Axios below 1.15.0 are affected by this vulnerability. Updating ensures the application uses a secure version.
Related Issue
Resolves: #431
Motivation and Context
A critical vulnerability (CVE-2025-62718) was identified in older versions of Axios.
Upgrading to >=1.15.0 mitigates this risk and ensures the project remains secure and up-to-date.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: