[Snyk] Security upgrade axios from 1.8.4 to 1.18.0

[peterj]

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
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-18060165
	Uncontrolled Recursion SNYK-JS-AXIOS-18060167
	Prototype Pollution SNYK-JS-AXIOS-18060659
	Uncontrolled Recursion SNYK-JS-AXIOS-18060730
	Prototype Pollution SNYK-JS-AXIOS-18065349
	Prototype Pollution SNYK-JS-AXIOS-18065351
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-18065353
	Prototype Pollution SNYK-JS-AXIOS-18065355

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

[peterj]

This is a significant minor version upgrade across 10 versions, from 1.8.4 to 1.18.0. While there are no mandatory API removals, there are several security-driven behavioral changes that require verification.

Key Changes:

• Stricter URL Validation: URLs that omit // (e.g., http:example.com) will now be rejected with an ERR_INVALID_URL error. Previously, these may have been handled more leniently. [2]
• Redirect Header Stripping: For security, sensitive headers (like Authorization) will now be automatically stripped when a request is redirected to a different origin. Applications that relied on these headers being forwarded during cross-origin redirects may see authentication failures. [2, 5]
• Numerous Fixes: This range includes dozens of bug fixes and security hardening updates related to proxies, redirects, headers, and error handling that could subtly change behavior in edge cases. [1]

Recommendation: Verify application behavior after the upgrade, paying close attention to requests involving redirects to other domains and any custom URL construction logic.

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.