[Snyk] Security upgrade axios from 1.12.2 to 1.18.0

[winjer]

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

[winjer]

This is a minor version upgrade that includes security hardening and behavioral changes that require verification.

Key Changes:

• Security Hardening: Multiple versions in this range introduce security fixes. Notably, v1.18.0 hardens redirect and URL handling. It now strips sensitive headers (like API keys) on cross-origin redirects and rejects malformed URLs that were previously accepted.
• Stricter Validation: The upgrade enforces stricter validation for URLs and request configurations. For example, malformed http: and https: URLs that omit // will now be rejected with an ERR_INVALID_URL error.
• Behavioral Change (validateStatus): Version 1.18.0 introduces a transitional.validateStatusUndefinedResolves option. This changes how requests with validateStatus: undefined are handled, making them behave as if the option was omitted. This could affect error handling if you relied on the previous behavior.

Recommendation:
Review your application's error handling, especially for requests involving redirects or potentially malformed URLs. Verify that custom authentication headers are not expected to be passed on cross-origin redirects. Test any logic that relies on the validateStatus configuration option.

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.