[Snyk] Security upgrade axios from 1.13.6 to 1.15.2

[rvu-snyk]

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

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	HTTP Response Splitting SNYK-JS-AXIOS-16298058	848
	Uncontrolled Recursion SNYK-JS-AXIOS-16299923	828
	Improperly Controlled Modification of Dynamically-Determined Object Attributes SNYK-JS-AXIOS-16299921	808
	Prototype Pollution SNYK-JS-AXIOS-16299904	741

Breaking Change Risk

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:

🦉 Prototype Pollution
🦉 Improperly Controlled Modification of Dynamically-Determined Object Attributes

[rvu-snyk]

This minor version upgrade for axios includes multiple security patches, bug fixes, and dependency updates across several versions.

Key Changes:

• Security Hardening: The releases from v1.14.0 to v1.15.2 introduce significant security enhancements. This includes stricter validation and sanitization of headers, hardening against prototype pollution vulnerabilities, fixes for Server-Side Request Forgery (SSRF), and improved handling of multipart data. [1, 2, 4, 6]
• Bug Fixes: A notable fix in v1.14.0 resolves a CommonJS compatibility regression that was introduced in v1.13.6. [3]
• Deprecation: The deprecated url.parse() has been replaced to resolve warnings in newer Node.js versions. [1]

Potential Impact:
While there are no explicit API breaking changes, the security hardening introduces stricter validation rules. Requests that previously worked with more lenient validation (e.g., certain header formats) may now be rejected. This constitutes a behavioral change that requires verification.

Recommendation:
Given the security-focused behavioral changes, it is recommended to test the upgrade to ensure that existing requests and configurations behave as expected.

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.