[pushkala-datastax]

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
	Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-21761837	740	io.debezium:debezium-core: 2.6.1.Final -> 3.5.0.Final org.apache.kafka:connect-runtime: 3.4.0 -> 4.0.0 org.apache.kafka:kafka_2.13: 3.4.0 -> 4.4.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

[pushkala-datastax]

This upgrade involves multiple high-impact major version changes, most notably for Apache Kafka, which requires significant architectural and environmental updates.

1. HIGH RISK: Apache Kafka (connect-runtime, kafka_2.13) 3.4.0 → 4.x

The upgrade to Apache Kafka 4.x is a major architectural overhaul with significant breaking changes. Direct upgrades will fail. Careful planning and a multi-stage migration are required.

Key Breaking Changes:

• ZooKeeper Removed: Kafka 4.0 and later run exclusively in KRaft mode. ZooKeeper mode is completely removed. Clusters must be migrated to KRaft before upgrading to version 4.0.
• Java 17 Required: Kafka Brokers and Kafka Connect now require Java 17 to run. Kafka Clients and Streams require a minimum of Java 11.
• API Removals: Many APIs that were deprecated in previous versions have been removed in 4.0. Code using these old APIs will break and must be updated.
• Jakarta EE Upgrade: Kafka Connect has been upgraded to use Jakarta EE 10 APIs, which may impact compatibility with other applications.

Recommendation: Do not merge this upgrade directly. A dedicated migration project is necessary. The standard path involves upgrading to an intermediate "bridge" release (e.g., Kafka 3.9) to migrate metadata from ZooKeeper to KRaft before finally upgrading to version 4.x.

Source: Apache Kafka 4.0 Release Notes, Debezium Blog

2. MEDIUM RISK: Debezium Core (debezium-core) 2.6.1 → 3.5.0

This major version upgrade for Debezium introduces a mandatory runtime environment change.

Key Breaking Changes:

• Java 17 Required: Debezium 3.x requires a Java 17 runtime environment for all connectors. Components like Debezium Server or Operator require Java 21.
• Kafka 3.8+ Baseline: Debezium 3.x is built and tested against Kafka 3.8+, adapting to internal API changes.

Recommendation: Ensure the production environment and any build pipelines are using Java 17 or newer before applying this upgrade. The risk is medium as it's an environment change that requires validation but is less complex than the Kafka architectural migration.

Source: Debezium 3.0 Release Blog

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