[Snyk] Security upgrade org.springframework.boot:spring-boot-starter-web from 4.0.0 to 4.0.7

[macroscope-cloud]

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

Snyk changed the following file(s):

• examples/iOS-Hybrid-App-Java-Server/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-TOOLSJACKSONCORE-18170128	828	org.springframework.boot:spring-boot-starter-web: 4.0.0 -> 4.0.7 Proof of Concept

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

[macroscope-cloud]

This is a patch version upgrade from 4.0.0 to 4.0.7. According to the official announcement, this release contains bug fixes, documentation improvements, and dependency upgrades.

Patch releases in Spring Boot are not intended to contain breaking API changes. This update addresses two security vulnerabilities, which may alter behavior in specific, insecure configurations:

• CVE-2026-40992: A fix for mail auto-configuration may cause connections to mail servers with invalid SSL certificates to fail, which is the correct and secure behavior.
• CVE-2026-41001: A fix for a predictable temporary directory in Artemis auto-configuration.

No breaking API changes are documented for this version range.

Recommendation: No immediate action is required, but it is always recommended to run regression tests after any dependency upgrade.

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