[Snyk] Security upgrade axios from 1.7.9 to 1.18.0

[pushkala-datastax]

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

Snyk changed the following file(s):

• src/frontend/package.json
• src/frontend/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	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
🦉 Prototype Pollution

[pushkala-datastax]

This upgrade spans multiple minor versions and introduces several security hardening measures that change request behavior, warranting verification.

Key Behavioral Changes:

• Stricter URL Validation: As of v1.18.0, requests with malformed URLs that omit // (e.g., http:example.com) will be rejected with an ERR_INVALID_URL error. Previously, these may have been accepted. [2, 5]
• Redirect Header Stripping (Node.js): For security, the Node.js adapter now strips sensitive headers (like Authorization or custom API keys) on cross-origin redirects. If your application relies on these headers being forwarded to a different origin, that functionality will break. [1, 2, 5]
• Status Validation: The behavior of validateStatus: undefined has been clarified, with a new transitional option available to opt into new semantics. [2]

Recommendation: Verify that all request URLs are correctly formatted. Review and test any application logic that involves cross-origin redirects where custom headers are expected to be forwarded.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.