[Snyk] Security upgrade org.springframework:spring-web from 6.2.17 to 6.2.19

[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:spring-web: 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]

This is a patch-level upgrade that includes numerous security fixes across versions 6.2.18 and 6.2.19.

Key Changes:

• Security Fixes: These releases address a large number of CVEs, including fixes for Denial of Service (DoS), Cross-Site Scripting (XSS), path traversal, and others.
• SpEL Hardening: To address an algorithmic DoS vulnerability (CVE-2026-41850), version 6.2.19 introduces a default limit of 10,000 operations for the evaluation of a Spring Expression Language (SpEL) expression. This is a security enhancement, but could be a breaking change for applications that rely on unusually complex expressions. The limit is configurable.
• JMS Deserialization: To address unsafe deserialization (CVE-2026-41855), new methods have been added to MappingJackson2MessageConverter to limit trusted packages. This is an additive change.

Recommendation:
While this is a patch release and intended to be non-breaking, the new default limit on SpEL expressions introduces a potential for behavioral change. It is recommended to verify that any complex SpEL expressions used in your application do not exceed the new default operation limit. Review the extensive list of CVEs fixed in these versions to ensure no security patch inadvertently affects your application's behavior.

Source: Spring Framework Release Notes

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