PatchTheCVEconnect for kafka vulnerabilities and fixes
Recent CVEs affecting connect for kafka, with upgrade or downgrade steps. 4 tracked.
Also searched as: connectforkafka.
connect for kafka has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2026-08-19. Highest priority: CVE-2026-76402 (score 43/100).
- CVE-2026-76400 MEDIUM 5.9 UPGRADE In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Repr
- CVE-2026-76401 MEDIUM 5.9 UPGRADE In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Repr
- CVE-2026-76402 HIGH 8.2 UPGRADE In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Repr
- CVE-2026-76403 HIGH 7.4 UPGRADE In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user positioned in the network path could
FAQ
How do I fix connect for kafka vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is connect for kafka being exploited right now?
None of the tracked connect for kafka CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which connect for kafka CVE should I patch first?
CVE-2026-76402 currently ranks highest (43/100): In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Repr.