[Snyk] Fix for 9 vulnerabilities

[schoenwaldnils]

Snyk has created this PR to fix 9 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Directory Traversal SNYK-JS-POSTCSS-18313038	721
	Server-side Request Forgery (SSRF) SNYK-JS-NEXT-18233136	701
	Server-side Request Forgery (SSRF) SNYK-JS-NEXT-18233752	701
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-18233133	696
	Improper Encoding or Escaping of Output SNYK-JS-NEXT-18230947	601
	Inefficient Algorithmic Complexity SNYK-JS-NEXT-18231604	601
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-18232299	601
	Insertion of Sensitive Information Into Sent Data SNYK-JS-NEXT-18233109	601
	Use of Cache Containing Sensitive Information SNYK-JS-NEXT-18233146	586

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
🦉 Server-side Request Forgery (SSRF)
🦉 Directory Traversal

[schoenwaldnils]

This update includes two patch-level changes. The postcss upgrade is assessed as medium risk due to a security hardening change that could affect specific build configurations.

Top Changes:

• postcss 8.5.16 → 8.5.18 (Medium Risk):

  • Version 8.5.18 introduces a security restriction on loading previous source map files. They are now confined to the opts.from folder by default.
  • Action/Verification: If your build process relies on loading source maps from outside the source folder, this may be a breaking change. You can disable this security check by setting opts.unsafeMap: true.
  • Version 8.5.17 included fixes for a "Maximum call stack size exceeded" error and a prototype hijacking vulnerability.

• next 16.2.10 → 16.2.11 (Low Risk):

  • This is a security release that patches several high-severity vulnerabilities, including Denial of Service (DoS), middleware bypass, and Server-Side Request Forgery (SSRF).
  • No breaking API changes are documented; it is intended as a direct, safe upgrade to maintain application security.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
schoen-world	Ready	Preview, v0	Aug 3, 2026 8:19am