[Snyk] Fix for 1 vulnerabilities

[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
	Deserialization of Untrusted Data SNYK-JAVA-ORGSPRINGFRAMEWORK-18326609	746	org.springframework.boot:spring-boot-starter-json: 3.5.13 -> 3.5.15 org.springframework:spring-web: 6.2.17 -> 6.2.19 org.springframework:spring-webmvc: 6.2.17 -> 6.2.19 No Known Exploit

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:

🦉 Deserialization of Untrusted Data

[macroscope-cloud]

These are patch-level upgrades for Spring Boot and Spring Framework, primarily containing bug fixes and significant security patches. No mandatory API changes are documented, but one security fix introduces a behavioral change that warrants a medium risk assessment.

Key Changes:

• spring-boot-starter-json (3.5.13 → 3.5.15): These updates correspond to Spring Boot patch releases. They include numerous bug fixes, dependency upgrades, and security patches without introducing breaking changes.

• spring-web & spring-webmvc (6.2.17 → 6.2.19): These Spring Framework updates address a large number of security vulnerabilities (CVEs).

Potential Behavioral Change:

• Spring Expression Language (SpEL) Limit: To address CVE-2026-41850, version 6.2.19 introduces a default limit of 10,000 operations for SpEL expression evaluation to prevent Denial of Service attacks. Applications using extremely complex SpEL expressions may encounter new exceptions. This limit is configurable if needed.

Recommendation:
While these upgrades are essential for security, developers should verify if their applications rely on very complex Spring Expression Language (SpEL) evaluations, as the new default operation limit could impact them. For the vast majority of applications, this upgrade should be safe and non-breaking.

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