How severe is GHSA-6jmf-mxwf-r3jc?

GHSA-6jmf-mxwf-r3jc has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6jmf-mxwf-r3jc?

GHSA-6jmf-mxwf-r3jc affects the following packages: org.apache.kafka:kafka (Maven), org.apache.kafka:kafka (Maven), org.apache.kafka:kafka (Maven), org.apache.kafka:kafka (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6jmf-mxwf-r3jc?

Update org.apache.kafka:kafka to 2.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6jmf-mxwf-r3jc is resolved across your whole dependency graph.

How do I detect GHSA-6jmf-mxwf-r3jc in my Maven dependencies?

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.

How do I mitigate GHSA-6jmf-mxwf-r3jc if there is no patch (or I can't update yet)?

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.

Is GHSA-6jmf-mxwf-r3jc actively exploited in the wild?

No public exploit code has been indexed for GHSA-6jmf-mxwf-r3jc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6jmf-mxwf-r3jc?

GHSA-6jmf-mxwf-r3jc has an EPSS (Exploit Prediction Scoring System) score of 3.9%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6jmf-mxwf-r3jc?

GHSA-6jmf-mxwf-r3jc is classified as CWE-319 (CWE-319). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6jmf-mxwf-r3jc published, and has it been updated?

GHSA-6jmf-mxwf-r3jc was published on May 12, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Exposure of Sensitive Information to an Unauthorized…

EPSS Exploitation Probability

via FIRST.org ↗

3.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

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

Real-World Exposure

4 pkgs affected

☕org.apache.kafka:kafka☕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

When Connect workers in Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, or 2.3.0 are configured with one or more config providers, and a connector is created/updated on that Connect cluster to use an externalized secret variable in a substring of a connector configuration property value, then any client can issue a request to the same Connect cluster to obtain the connector's task configuration and the response will contain the plaintext secret rather than the externalized secrets variables.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.kafka:kafka`	≥ 2.0.0&&< 2.0.2	2.0.2`org.apache.kafka:kafka:2.0.2`
☕Maven	`org.apache.kafka:kafka`	≥ 2.1.0&&< 2.1.2	2.1.2`org.apache.kafka:kafka:2.1.2`
☕Maven	`org.apache.kafka:kafka`	≥ 2.2.0&&< 2.2.2	2.2.2`org.apache.kafka:kafka:2.2.2`
☕Maven	`org.apache.kafka:kafka`	≥ 2.3.0&&< 2.3.1	2.3.1`org.apache.kafka:kafka:2.3.1`

Affected Products

13 products · 27 configurations

Application

kafkaapache

7 versions

2.0.02.0.12.1.02.1.12.2.02.2.12.3.0

Application

banking corporate lending process managementoracle

3 versions

14.1.014.3.014.4.0

Application

banking credit facilities process managementoracle

3 versions

14.1.014.3.014.4.0

Application

banking liquidity managementoracle

≥ 14.0.0 && ≤ 14.4.0

range

Application

banking paymentsoracle

1 version

14.4.0

Application

banking platformoracle

1 version

2.7.0

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update org.apache.kafka:kafka to 2.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6jmf-mxwf-r3jc is resolved across your whole dependency graph.
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

Product	Fixed in	Advisory
Red Hat AMQ Streams 1	`kafka`	RHSA-2020:0939

Frequently Asked Questions

When Connect workers in Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, or 2.3.0 are configured with one or more config providers, and a connector is created/updated on that Connect cluster to use an externalized secret variable in a substring of a connector configuration property value, then any client can issue a request to the same Connect cluster to obtain the connector's task configuration and the response will contain the plaintext secret rather than the externalized secrets variables.

O3 Security · Impact-Aware SCA

Is GHSA-6jmf-mxwf-r3jc in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Exposure of Sensitive Information to an Unauthorized Actor in Apache KafkaGHSA-6jmf-mxwf-r3jc

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is GHSA-6jmf-mxwf-r3jc in your dependencies?