Skip to content

[Snyk] Upgrade axios from 1.4.0 to 1.12.2 #194

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.12.2 #194

codingdud wants to merge 1 commit into from

Conversation

@codingdud
Copy link
Owner

@codingdud codingdud commented Oct 12, 2025

snyk-top-banner

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

ℹ️ 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 35 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.12.2
b31f7c6 
Snyk has created this PR to upgrade axios from 1.4.0 to 1.12.2.

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 Oct 12, 2025 •
edited
Loading

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

Project Deployment Preview Comments Updated (UTC)
simpform Error Error Oct 12, 2025 8:32am

@gemini-code-assist
Copy link

gemini-code-assist bot commented Oct 12, 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, updates the axios dependency to its latest stable version, 1.12.2. The primary motivation for this upgrade is to enhance the project's security posture by patching several known vulnerabilities and to ensure the project benefits from the latest bug fixes and features in the axios library.

Highlights

  • Core Dependency Upgrade: The axios package has been upgraded from version 1.4.0 to 1.12.2, a significant update spanning 35 minor versions.
  • Critical Security Vulnerability Resolution: This upgrade directly addresses nine security vulnerabilities, including high-severity issues like Cross-site Request Forgery (CSRF), Prototype Pollution, and Server-side Request Forgery (SSRF), as well as medium-severity concerns such as Regular Expression Denial of Service (ReDoS).
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 Oct 12, 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, automatically generated by Snyk, upgrades the axios dependency from version 1.4.0 to 1.12.2. This is a crucial update that resolves multiple high and medium severity security vulnerabilities, including Cross-site Request Forgery (CSRF), Prototype Pollution, and Server-side Request Forgery (SSRF). The change is correct and necessary. I've added one suggestion to consider a stricter version constraint for axios to enhance future stability. Given the significant version jump, it is highly recommended to perform thorough regression testing on a staging environment before merging this into the main branch to ensure no breaking changes affect the application's functionality.

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

@gemini-code-assist gemini-code-assist bot Oct 12, 2025

Choose a reason for hiding this comment

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

medium

For better stability and to avoid potential breaking changes from minor version updates, consider using a tilde ~ instead of a caret ^ for the axios version. This will lock the version to patch releases (1.12.x) instead of allowing any minor update (1.x.x), reducing the risk of unexpected issues in this critical dependency.

Suggested change
"axios": "^1.12.2",
"axios": "~1.12.2",

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