Skip to content

[Snyk] Upgrade axios from 1.4.0 to 1.13.1 #195

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
codingdud wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Upgrade axios from 1.4.0 to 1.13.1 #195

codingdud wants to merge 1 commit into from

Conversation

@codingdud
Copy link
Owner

@codingdud codingdud commented Nov 23, 2025

snyk-top-banner

Snyk has created this PR to upgrade axios from 1.4.0 to 1.13.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 37 versions ahead of your current version.

  • The recommended version was released a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Cross-site Request Forgery (CSRF)
SNYK-JS-AXIOS-6032459		 666 Proof of Concept
high severity Prototype Pollution
SNYK-JS-AXIOS-6144788		 666 No Known Exploit
high severity Server-side Request Forgery (SSRF)
SNYK-JS-AXIOS-7361793		 666 Proof of Concept
high severity Improper Handling of Extra Parameters
SNYK-JS-FOLLOWREDIRECTS-6141137		 666 Proof of Concept
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-AXIOS-12613773		 666 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-AXIOS-6124857		 666 Proof of Concept
medium severity Server-side Request Forgery (SSRF)
SNYK-JS-AXIOS-9292519		 666 Proof of Concept
medium severity Server-side Request Forgery (SSRF)
SNYK-JS-AXIOS-9403194		 666 No Known Exploit
medium severity Information Exposure
SNYK-JS-FOLLOWREDIRECTS-6444610		 666 Proof of Concept
Release notes
Package name: axios from axios GitHub release notes

Important

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

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

For more information:

@snyk-bot
fix: upgrade axios from 1.4.0 to 1.13.1
8f1cf57 
Snyk has created this PR to upgrade axios from 1.4.0 to 1.13.1.

See this package in npm:
axios

See this project in Snyk:
https://app.snyk.io/org/codingdud/project/fbe45036-7a9d-4ede-9cf4-9331e0bb4a97?utm_source=github&utm_medium=referral&page=upgrade-pr
@vercel
Copy link

vercel bot commented Nov 23, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
simpform Error Error Nov 23, 2025 7:31am

@gemini-code-assist
Copy link

gemini-code-assist bot commented Nov 23, 2025

Summary of Changes

Hello @codingdud, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the security and stability of the project by upgrading the 'axios' HTTP client library from version '1.4.0' to '1.13.1'. This significant update resolves a range of critical and moderate security vulnerabilities and introduces various bug fixes and new features accumulated over 37 versions, ensuring the application benefits from the latest improvements and protections.

Highlights

  • Dependency Upgrade: Upgrades the 'axios' package from version '1.4.0' to '1.13.1', incorporating 37 new versions.
  • Security Fixes: Addresses multiple high and medium severity vulnerabilities, including Cross-site Request Forgery (CSRF), Prototype Pollution, Server-side Request Forgery (SSRF), Improper Handling of Extra Parameters, Allocation of Resources Without Limits or Throttling, Regular Expression Denial of Service (ReDoS), and Information Exposure.
  • Transitive Dependency Updates: Updates several transitive dependencies such as 'follow-redirects', 'form-data', 'function-bind', 'get-intrinsic', 'gopd', 'has-symbols', 'has-tostringtag', and 'es-set-tostringtag', and introduces new ones like 'call-bind-apply-helpers', 'dunder-proto', 'es-define-property', 'es-errors', 'es-object-atoms', 'get-proto', 'hasown', and 'math-intrinsics'.
  • New Features and Bug Fixes: Incorporates numerous bug fixes and new features from the updated 'axios' versions, including HTTP2 support, improved fetch adapter options, and various type definition enhancements.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist[bot]
gemini-code-assist bot reviewed Nov 23, 2025
View reviewed changes
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request upgrades axios from version 1.4.0 to 1.13.1. This is an important security update that resolves multiple vulnerabilities, including Cross-site Request Forgery (CSRF), Prototype Pollution, and Server-side Request Forgery (SSRF). While this is a minor version upgrade, it spans 37 individual releases. I have added a comment regarding a specific change in URL parameter encoding in axios@1.12.0 which could be a potential breaking change. Given the large version jump, thorough end-to-end testing of features that rely on axios is highly recommended to ensure no regressions are introduced.

frontend/package.json
"@testing-library/react": "^13.4.0",
"@testing-library/user-event": "^13.5.0",
"axios": "^1.4.0",
"axios": "^1.13.1",
Copy link

@gemini-code-assist gemini-code-assist bot Nov 23, 2025

Choose a reason for hiding this comment

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

high

The upgrade to axios@1.13.1 is a large version jump. It's worth noting that axios@1.12.0 introduced a change to how URL parameters are encoded. Specifically, [ and ] characters are now URL-encoded in query parameters to better align with RFC3986. This may affect how array parameters are sent and interpreted by your backend, especially if it has specific expectations for the format of array parameters (e.g., param[]=value1&param[]=value2). This change could potentially introduce subtle bugs if your backend parsing is strict.

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

Reviewers

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@codingdud @snyk-bot