[Snyk] Security upgrade werkzeug from 2.2.3 to 3.1.4

[MaKyOtOx]

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• engines/arachni/requirements.txt

⚠️ Warning

Flask 2.2.3 requires Werkzeug, which is not installed.

---

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.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

---

Note

Bumps werkzeug from 2.2.3 to 3.1.4 in engines/arachni/requirements.txt.

^{Written by Cursor Bugbot for commit abf58fe. This will update automatically on new commits. Configure here.}

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: Werkzeug 3.x incompatible with Flask 2.2.3

Upgrading werkzeug to version 3.1.4 while Flask remains at 2.2.3 creates a dependency incompatibility. Flask 2.x was designed to work with Werkzeug 2.x, and Werkzeug 3.0 introduced breaking API changes. This version mismatch can cause runtime errors when Flask attempts to use changed or removed Werkzeug APIs. The PR description itself contains a warning about this issue. Either Flask needs to be upgraded to 3.x alongside this change, or werkzeug needs to stay within the 2.x series.