[Snyk] Fix for 1 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• debezium-server/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Use of Cache Containing Sensitive Information SNYK-JAVA-IONETTY-18956131	130	software.amazon.awssdk:kinesis: 2.13.13 -> 2.52.1 Major version upgrade No Path Found No Known Exploit

Breaking Change Risk

Notice: This assessment is enhanced by AI.

Vulnerabilities that could not be fixed

• Upgrade:
  • Could not upgrade io.quarkus:quarkus-smallrye-health@1.4.1.Final to io.quarkus:quarkus-smallrye-health@2.3.0.Final; Reason could not apply upgrade, dependency is managed externally ; Location: provenance does not contain location

---

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.

[snyk-io]

This upgrade has a high risk of breaking changes due to the major version jump in io.quarkus:quarkus-smallrye-health.

io.quarkus:quarkus-smallrye-health@1.4.1.Final → 2.3.0.Final

Risk: HIGH

This is a major upgrade from Quarkus 1.x to 2.x, which introduces significant breaking changes.

Key Breaking Changes:

• Java 11 Required: Quarkus 2.0 and later require a minimum of JDK 11. JDK 8 is no longer supported. [1, 5]
• Health Endpoint Path Change: Non-application endpoints, including health checks, are now exposed under the /q path prefix by default (e.g., /q/health). The previous property to disable this behavior has been removed. [1]
• MicroProfile Health 3.0: Quarkus 2.x implements MicroProfile Health 3.0, which formalizes the distinction between liveness (/q/health/live) and readiness (/q/health/ready) probes. The old /health endpoint is deprecated. [5, 10, 13]

Recommendation:

1. Ensure your environment is running on JDK 11 or newer.
2. Update any consumers of the health endpoint (like Kubernetes probes or monitoring tools) to use the new /q/health/live and /q/health/ready paths.
3. To restore the previous behavior and remove the /q prefix, you must explicitly configure the root path in your application.properties: quarkus.smallrye-health.root-path=/health. [1]

Source: Quarkus 2.0 Migration Guide

software.amazon.awssdk:kinesis@2.13.13 → 2.52.1

Risk: LOW

This is a minor version upgrade within the AWS SDK for Java v2 series. The SDK maintains backward compatibility within a major version. The changes between these versions primarily consist of feature additions, performance improvements, and bug fixes. No breaking changes for the Kinesis client were identified in the official changelogs for this version range. [9, 15]

Source: AWS SDK for Java v2 Changelog

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

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.