Skip to content
Fencer Vulns
high 8.8

CVE-2018-17196 json

Improper Input Validation in Apache Kafka

published 2019-07-11 7 y ago modified 2026-06-17 4 mo ago also GHSA-47w3-66wq-cpxg , EUVD-2022-2333

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.4%
EPSS 5.4% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

In Apache Kafka versions between 0.11.0.0 and 2.1.0, it is possible to manually craft a Produce request which bypasses transaction/idempotent ACL validation. Only authenticated clients with Write permission on the respective topics are able to exploit this vulnerability. Users should upgrade to 2.1.1 or later where this vulnerability has been fixed.

Patch / fix

  • maven org.apache.kafka:kafka 2.1.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-17196 updated cvss 8.8

kafka: potential to bypass transaction/idempotent ACL checks

  • Red Hat Mobile Application Platform 4 kafka
    affected: no fix planned “Out of support scope”
  • Red Hat Fuse 7 kafka Red Hat JBoss Fuse 6 kafka Red Hat OpenShift Application Runtimes kafka Red Hat streams for Apache Kafka kafka
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

5.38% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.kafka:kafka
>=0.11.0.0, <2.1.1
2.1.1

Affected products

  • Apache Kafka

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.