NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Improper Control of Generation of Code in Apache KafkaGHSA-gh27-38p5-mrxc

MEDIUM

GHSA-gh27-38p5-mrxc is a medium-severity (CVSS 5.4) vulnerability in org.apache.kafka:kafka. A fix is available for org.apache.kafka:kafka — see the affected versions and patch details below.

Also known asCVE-2018-1288
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk
0.00%2.01%4.02%6.03%0.7%4.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
☕org.apache.kafka:kafka☕org.apache.kafka:kafka☕org.apache.kafka:kafka

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

In Apache Kafka 0.9.0.0 to 0.9.0.1, 0.10.0.0 to 0.10.2.1, 0.11.0.0 to 0.11.0.2, and 1.0.0, authenticated Kafka users may perform action reserved for the Broker via a manually created fetch request interfering with data replication, resulting in data loss.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.kafka:kafka≥ 0.9.0.0&&< 0.10.2.20.10.2.2org.apache.kafka:kafka:0.10.2.2
☕Mavenorg.apache.kafka:kafka≥ 0.11.0.0&&< 0.11.0.30.11.0.3org.apache.kafka:kafka:0.11.0.3
☕Mavenorg.apache.kafka:kafka≥ 1.0.0&&< 1.0.11.0.1org.apache.kafka:kafka:1.0.1

Affected Products

5 products · 12 configurations
Application
kafkaapache
≥ 0.11.0.0 && ≤ 0.11.0.2
1 version
1.0.0
Application
databaseoracle
5 versions
11.2.0.412.1.0.212.2.0.118c19c
Application
primavera p6 enterprise project portfolio managementoracle
≥ 19.12.0.0 && ≤ 19.12.6.0
range
Application
timesten in-memory databaseoracle
< 18.1.2.1.0
range
Application
jboss middleware text-only advisoriesredhat
1 version
1.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.kafka:kafka, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.kafka:kafka to 0.10.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gh27-38p5-mrxc is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat Fuse 7.2kafkaRHSA-2018:3768

Frequently Asked Questions

In Apache Kafka 0.9.0.0 to 0.9.0.1, 0.10.0.0 to 0.10.2.1, 0.11.0.0 to 0.11.0.2, and 1.0.0, authenticated Kafka users may perform action reserved for the Broker via a manually created fetch request interfering with data replication, resulting in data loss.
O3 Security · Impact-Aware SCA

Is GHSA-gh27-38p5-mrxc in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper Control of Generation of Code in Apache Kafka