[Snyk] Security upgrade org.apache.kafka:connect-api from 2.5.0 to 3.9.2

[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
	NULL Pointer Dereference SNYK-JAVA-ORGLZ4-18313067	131	org.apache.kafka:connect-api: 2.5.0 -> 3.9.2 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:

🦉 NULL Pointer Dereference

[snyk-io]

This major version upgrade from 2.5.0 to 3.9.2 introduces significant breaking changes, configuration changes, and deprecations.

High Risk Breaking Changes:

• Removal of Internal Converter Properties: The internal.key.converter and internal.value.converter properties for Connect workers, deprecated since Kafka 2.0, have been removed. The system now defaults to JsonConverter. If you were using these properties, your Connect cluster will fail to start without updating the configuration. [8]

Medium Risk Changes (Verification Required):

• New Producer Defaults: Producers now enable the strongest delivery guarantees by default (enable.idempotence=true and acks=all). [4, 6, 8] This is a behavioral change that could affect throughput and requires connectors to be compatible with idempotent producers.
• Connector Client Overrides: Client configuration overrides for connectors are now enabled by default. [1] This changes the security posture and may alter connector behavior if not explicitly configured.
• Java 8 Deprecation: Support for Java 8 is deprecated in version 3.0.0 and is scheduled for removal in Kafka 4.0.0. [1, 4, 6] While not an immediate break, an upgrade to Java 11 or later is required to stay on a supported path.

Recommendation:
Before merging, you must review your Kafka Connect worker configurations and remove any instances of internal.key.converter and internal.value.converter. [8] It is also critical to test your connectors to ensure they are compatible with the new idempotent producer defaults and the policy for client overrides. Plan a migration to a Java 11+ runtime environment.

Source: Apache Kafka Release Notes. [1, 4, 8]

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

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

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