[Snyk] Security upgrade axios from 1.11.0 to 1.12.0

[maidul98]

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

Snyk changed the following file(s):

• backend/package.json
• backend/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-12613773	738

---

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:

🦉 Allocation of Resources Without Limits or Throttling

[maidul98]

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

✅ security/snyk check is complete. No issues have been found. (View Details)

[greptile-apps]

Greptile Summary

This PR is an automated security upgrade created by Snyk that updates the axios dependency from version 1.11.0 to 1.12.0 in the backend package.json. The upgrade addresses a medium-severity vulnerability (SNYK-JS-AXIOS-12613773) related to "Allocation of Resources Without Limits or Throttling" with a severity score of 738/1000.

The axios library is a core HTTP client used extensively throughout Infisical's backend for making API requests to external services, integrations, and internal communication. This makes it a critical dependency whose security directly impacts the entire application's security posture. The vulnerability being fixed relates to resource allocation controls, which could potentially be exploited to cause resource exhaustion attacks.

This is a patch-level update (1.11.0 → 1.12.0) which typically indicates backward compatibility, and the PR metadata confirms this is not a breaking change. The fix involves only updating the version number in the dependencies section of package.json, along with the corresponding package-lock.json updates.

Confidence score: 5/5

• This PR is safe to merge with minimal risk as it's a patch-level security update for a critical vulnerability
• Score reflects the straightforward nature of a dependency security patch with no breaking changes indicated
• No files require special attention as this is a standard dependency version bump

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}