[Snyk] Security upgrade axios from 1.8.1 to 1.18.0

[hubert-stefaniak]

Snyk has created this PR to fix 8 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
	Uncontrolled Recursion SNYK-JS-AXIOS-18060730	738
	Prototype Pollution SNYK-JS-AXIOS-18065351	738
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-18060165	708
	Uncontrolled Recursion SNYK-JS-AXIOS-18060167	708
	Prototype Pollution SNYK-JS-AXIOS-18060659	708
	Prototype Pollution SNYK-JS-AXIOS-18065349	708
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-18065353	708
	Prototype Pollution SNYK-JS-AXIOS-18065355	708

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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Uncontrolled Recursion
🦉 Prototype Pollution

[hubert-stefaniak]

This upgrade from axios v1.8.1 to v1.18.0 spans multiple minor versions and introduces several notable changes and security hardeings that require verification.

Highlights:

• Security Hardening: Multiple versions in this range introduce stricter validation and security fixes. For example, v1.18.0 hardens redirect and URL handling, rejecting malformed URLs that might have been implicitly accepted before. It also adds protections against leaking sensitive headers on cross-origin redirects.
• Configuration Changes: The validateStatus configuration semantics have been improved in v1.18.0. A new transitional option, validateStatusUndefinedResolves, has been added to help with backward compatibility.
• Potential Behavioral Changes:
  • The fetch adapter now enforces maxBodyLength and maxContentLength.
  • Proxy requests now preserve user-supplied Host headers.
  • The parseProtocol function now strictly requires a colon in the protocol separator.

Recommendation:
While no major API removals are cited, the cumulative effect of security hardening and stricter input validation could impact applications that rely on previous, more lenient behaviors. It is recommended to test application functionality related to URL parsing, redirects, and proxy usage after the upgrade. Review the changelogs for the intermediate versions to understand the full scope of changes.

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.