[Snyk] Security upgrade org.apache.kafka:connect-runtime from 2.5.0 to 4.0.0

[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

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Incorrect Implementation of Authentication Algorithm SNYK-JAVA-ORGECLIPSEJETTY-18230938	125	org.apache.kafka:connect-runtime: 2.5.0 -> 4.0.0 Major version upgrade No Path Found 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:

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

[snyk-io]

This is a major version upgrade from 2.5.0 to 4.0.0, which spans two major releases (3.x and 4.x) and introduces fundamental, high-impact breaking changes. A direct upgrade is not feasible and requires a carefully planned, multi-stage migration.

Key Breaking Changes:

• Complete Removal of ZooKeeper: The most significant change is that Apache Kafka 4.0.0 and later versions operate exclusively in KRaft mode, completely removing support for ZooKeeper. [3, 5, 9, 10] Any cluster running version 2.5.0 is dependent on ZooKeeper and must be migrated to KRaft before upgrading to 4.0.0. The recommended upgrade path involves upgrading to an intermediate 3.x version (like 3.9.x) to perform the migration, and only then upgrading to 4.0.0. [10, 15]

• Java 17 Runtime Required: Kafka Connect 4.0.0 requires Java 17 as the runtime environment. [3, 6, 17] This is a major jump from version 2.5.0, which supported Java 8. The environment hosting Kafka Connect must be upgraded.

• Jakarta EE API Upgrade: Kafka Connect has been upgraded to use Jakarta EE 10 APIs (KIP-1032). [3] This change replaces older javax.* packages with jakarta.* packages and will likely break any custom connectors, transforms, or converters that have not been updated.

• API and Protocol Removals: Many APIs that were deprecated in previous versions have been removed in 4

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

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

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