[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):

• pom.xml
• debezium-testing/debezium-testing-openshift/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-19496766	147	com.fasterxml.jackson.core:jackson-databind: 2.10.0 -> 2.18.10 io.fabric8:openshift-client: 4.6.4 -> 6.0.0 io.strimzi:api: 0.16.2 -> 0.23.0 Major version upgrade No Path Found 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:

🦉 Deserialization of Untrusted Data

[snyk-io]

This upgrade includes multiple high-risk changes, notably for io.fabric8:openshift-client and io.strimzi:api, which require significant developer action and migration steps. The jackson-databind upgrade also carries a medium risk due to a large version span.

io.fabric8:openshift-client 4.6.4 → 6.0.0 (HIGH RISK)

This is a major version upgrade from 4.x to 6.x, introducing significant breaking changes. A direct upgrade requires migrating across two major versions (v5 and v6).

Key Breaking Changes:

• Java 11 Required: The Java baseline was raised from 8 to 11 in version 6.0.
• API and DSL Overhaul: The client instantiation and resource manipulation DSL have changed significantly. Direct instantiation with new DefaultOpenShiftClient() is discouraged. The create() method is deprecated in favor of a new resource(item).create() pattern.
• API/Implementation Split: The library is now split into openshift-client-api and openshift-client modules. You should use the KubernetesClientBuilder for instantiation.
• Package Structure: Some OpenShift configuration models have been moved to a new package (io.fabric8.openshift.api.model.config.v1).
• Behavioral Changes: The delete() operation is now non-blocking by default.

Recommendation:
Developers must carefully follow the official v5 and v6 migration guides. Code must be refactored to use the new KubernetesClientBuilder, adapt to the new resource DSL, and verify compatibility with Java 11. This is a major effort that requires significant testing.

Source: Fabric8 v6 Migration Guide, Fabric8 v5 Migration Guide.

io.strimzi:api 0.16.2 → 0.23.0 (HIGH RISK)

This upgrade requires a mandatory migration of Custom

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 failed. 1 issues have been found so far.

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

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