How severe is CVE-2025-30677?

No CVSS score has been assigned to CVE-2025-30677 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-30677?

CVE-2025-30677 affects the following packages: org.apache.pulsar:pulsar-io-kafka-connect-adaptor (Maven), org.apache.pulsar:pulsar-io-kafka-connect-adaptor (Maven), org.apache.pulsar:pulsar-io-kafka-connect-adaptor (Maven), org.apache.pulsar:pulsar-io-kafka (Maven), org.apache.pulsar:pulsar-io-kafka (Maven), org.apache.pulsar:pulsar-io-kafka (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-30677?

Update org.apache.pulsar:pulsar-io-kafka-connect-adaptor to 3.0.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-30677 is resolved across your whole dependency graph.

How do I detect CVE-2025-30677 in my Maven dependencies?

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

How do I mitigate CVE-2025-30677 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.

How does O3 Security protect against CVE-2025-30677?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-30677 can be triaged on real exposure rather than presence alone.

Is CVE-2025-30677 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-30677 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 CVE-2025-30677?

CVE-2025-30677 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th 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 CVE-2025-30677?

CVE-2025-30677 is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-30677 published, and has it been updated?

CVE-2025-30677 was published on April 9, 2025 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2025-30677 — pulsar-io-kafka-connect-a…

CVE-2025-30677 is a CWE-532 vulnerability in org.apache.pulsar:pulsar-io-kafka-connect-adaptor. A fix is available for org.apache.pulsar:pulsar-io-kafka-connect-adaptor — see the affected versions and patch details below.

Apache Pulsar IO Kafka Connector, Apache Pulsar IO Kafka Connect Adaptor: Sensitive information logged in Pulsar's Apache Kafka Connectors

Also known asGHSA-rcqj-3fmp-5cqx

Published

Apr 9, 2025

Updated

Aug 12, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-30677.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

6 pkgs affected

☕org.apache.pulsar:pulsar-io-kafka-connect-adaptor☕org.apache.pulsar:pulsar-io-kafka-connect-adaptor☕org.apache.pulsar:pulsar-io-kafka-connect-adaptor☕org.apache.pulsar:pulsar-io-kafka☕org.apache.pulsar:pulsar-io-kafka☕org.apache.pulsar:pulsar-io-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

This vulnerability can lead to unintended exposure of credentials in log files, potentially allowing attackers with access to these logs to obtain Apache Kafka credentials. The vulnerability's impact is limited by the fact that an attacker would need access to the application logs to exploit this issue.

This issue affects Apache Pulsar IO's Apache Kafka connectors in all versions before 3.0.11, 3.3.6, and 4.0.4.

3.0.x version users should upgrade to at least 3.0.11.

3.3.x version users should upgrade to at least 3.3.6.

4.0.x version users should upgrade to at least 4.0.4.

Users operating versions prior to those listed above should upgrade to the aforementioned patched versions or newer versions.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.pulsar:pulsar-io-kafka-connect-adaptor`	all versions	3.0.11`org.apache.pulsar:pulsar-io-kafka-connect-adaptor:3.0.11`
☕Maven	`org.apache.pulsar:pulsar-io-kafka-connect-adaptor`	≥ 3.3.0&&< 3.3.6	3.3.6`org.apache.pulsar:pulsar-io-kafka-connect-adaptor:3.3.6`
☕Maven	`org.apache.pulsar:pulsar-io-kafka-connect-adaptor`	≥ 4.0.0&&< 4.0.4	4.0.4`org.apache.pulsar:pulsar-io-kafka-connect-adaptor:4.0.4`
☕Maven	`org.apache.pulsar:pulsar-io-kafka`	all versions	3.0.11`org.apache.pulsar:pulsar-io-kafka:3.0.11`
☕Maven	`org.apache.pulsar:pulsar-io-kafka`	≥ 3.3.0&&< 3.3.6	3.3.6`org.apache.pulsar:pulsar-io-kafka:3.3.6`
☕Maven	`org.apache.pulsar:pulsar-io-kafka`	≥ 4.0.0&&< 4.0.4	4.0.4`org.apache.pulsar:pulsar-io-kafka:4.0.4`

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.pulsar:pulsar-io-kafka-connect-adaptor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.pulsar:pulsar-io-kafka-connect-adaptor to 3.0.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-30677 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-30677 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-30677. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Apache Pulsar contains multiple connectors for integrating with Apache Kafka. The Pulsar IO Apache Kafka Source Connector, Sink Connector, and Kafka Connect Adaptor Sink Connector log sensitive configuration properties in plain text in application logs. This vulnerability can lead to unintended exposure of credentials in log files, potentially allowing attackers with access to these logs to obtain Apache Kafka credentials. The vulnerability's impact is limited by the fact that an attacker would need access to the application logs to exploit this issue. This issue affects Apache Pulsar IO's

O3 Security · Impact-Aware SCA

Is CVE-2025-30677 in your dependencies?

O3 Security finds CVE-2025-30677 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works