Skip to content

[Snyk] Security upgrade axios from 1.13.5 to 1.15.0#511

Open
graymalkin77 wants to merge 1 commit intomasterfrom
snyk-fix-4bf6ebb1e9c591a8682741f0ff474ae1
Open

[Snyk] Security upgrade axios from 1.13.5 to 1.15.0#511
graymalkin77 wants to merge 1 commit intomasterfrom
snyk-fix-4bf6ebb1e9c591a8682741f0ff474ae1

Conversation

@graymalkin77
Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
critical severity Unintended Proxy or Intermediary ('Confused Deputy')
SNYK-JS-AXIOS-15965856
  848  
high severity HTTP Response Splitting
SNYK-JS-AXIOS-15969258
  636  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@graymalkin77
Copy link
Copy Markdown
Author

Merge Risk: High

This upgrade to axios v1.15.0 includes security fixes but also introduces a breaking change related to configuration merging to prevent prototype pollution.

Breaking Change in v1.15.0

As part of a security fix, Axios now blocks the merging of the __proto__ key within configuration objects. According to the release notes, if your application relies on "unconventional deep-merging patterns that target the object prototype via Axios config, those operations will now be blocked." [2]

Other Changes

  • v1.15.0: Includes critical security patches for Server-Side Request Forgery (SSRF) and Header Injection, and adds support for Deno and Bun runtimes. [2, 4]
  • v1.14.0: This version did not have breaking changes but recommended users validate their integration if they rely on environment-based proxy behavior or specific CommonJS resolution edge cases. [2, 5]

Recommendation:
Review your Axios configurations to ensure you are not using deep-merging patterns that modify object prototypes. Given this is a security-driven change, it is a necessary upgrade, but verification is required.

Source: GitHub Releases

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Copilot AI review requested due to automatic review settings April 10, 2026 23:47
@graymalkin77
Copy link
Copy Markdown
Author

graymalkin77 commented Apr 10, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the axios dependency to remediate Snyk-reported vulnerabilities in the project’s npm dependency tree.

Changes:

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
package.json Updates the declared axios dependency range to a patched version.
package-lock.json Aligns the lockfile with the new axios version and updated transitive dependencies.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants