[Snyk] Security upgrade ch.qos.logback:logback-classic from 1.3.15 to 1.5.25

[jrialland]

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

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	External Initialization of Trusted Variables or Data Stores SNYK-JAVA-CHQOSLOGBACK-15062482	376	ch.qos.logback:logback-classic: 1.3.15 -> 1.5.25 No Known Exploit

---

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:

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

[Copilot]

Pull request overview

This PR upgrades the Logback library from version 1.3.15 to 1.5.25 to address a security vulnerability (SNYK-JAVA-CHQOSLOGBACK-15062482) related to external initialization of trusted variables or data stores.

Changes:

• Updated logback.version property from 1.3.15 to 1.5.25 in pom.xml

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Upgrading Logback to version 1.5.25 requires also upgrading SLF4J to version 2.0.x or later. Logback 1.5.x is built against SLF4J 2.0 API and is not compatible with SLF4J 1.7.x (currently at 1.7.36 on line 90). This mismatch will likely cause runtime errors or ClassNotFoundException issues. Consider upgrading slf4j.version to at least 2.0.0, or use Logback 1.3.x series (such as 1.3.16) which is compatible with SLF4J 1.7.x and also addresses the security vulnerability.

Suggested change

	<slf4j.version>1.7.36</slf4j.version>
	<slf4j.version>2.0.16</slf4j.version>