How severe is GHSA-47r2-phr8-m8cp?

GHSA-47r2-phr8-m8cp has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-47r2-phr8-m8cp?

GHSA-47r2-phr8-m8cp affects the following packages: org.apache.pulsar:pulsar-broker (Maven), org.apache.pulsar:pulsar-broker (Maven). Ecosystems affected: Maven.

How do I fix GHSA-47r2-phr8-m8cp?

Update org.apache.pulsar:pulsar-broker to 2.10.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-47r2-phr8-m8cp is resolved across your whole dependency graph.

How do I detect GHSA-47r2-phr8-m8cp in my Maven dependencies?

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

How do I mitigate GHSA-47r2-phr8-m8cp if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-47r2-phr8-m8cp actively exploited in the wild?

No public exploit code has been indexed for GHSA-47r2-phr8-m8cp 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-47r2-phr8-m8cp?

GHSA-47r2-phr8-m8cp has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th 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-47r2-phr8-m8cp?

GHSA-47r2-phr8-m8cp is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-47r2-phr8-m8cp published, and has it been updated?

GHSA-47r2-phr8-m8cp was published on July 12, 2023 and was last updated on February 16, 2024. 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

MEDIUM severity

GHSA-47r2-phr8-m8cp — pulsar-broker

MEDIUM

GHSA-47r2-phr8-m8cp is a medium-severity (CVSS 6.5) Improper Authentication vulnerability in org.apache.pulsar:pulsar-broker. A fix is available for org.apache.pulsar:pulsar-broker — see the affected versions and patch details below.

Apache Pulsar Broker Improper Authentication vulnerability

Also known asCVE-2023-31007

Published

Jul 12, 2023

Updated

Feb 16, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 26, 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 GHSA-47r2-phr8-m8cp.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-47r2-phr8-m8cp by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

☕org.apache.pulsar:pulsar-broker☕org.apache.pulsar:pulsar-broker

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

Improper Authentication vulnerability in Apache Software Foundation Apache Pulsar Broker allows a client to stay connected to a broker after authentication data expires if the client connected through the Pulsar Proxy when the broker is configured with authenticateOriginalAuthData=false or if a client connects directly to a broker with a specially crafted connect command when the broker is configured with authenticateOriginalAuthData=false.

This issue affects Apache Pulsar: through 2.9.4, from 2.10.0 through 2.10.3, 2.11.0.

2.9 Pulsar Broker users should upgrade to at least 2.9.5. 2.10 Pulsar Broker users should upgrade to at least 2.10.4. 2.11 Pulsar Broker users should upgrade to at least 2.11.1. 3.0 Pulsar Broker users are unaffected. Any users running the Pulsar Broker for 2.8.* and earlier should upgrade to one of the above patched versions.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.pulsar:pulsar-broker`	≥ 2.9.0&&< 2.10.4	2.10.4`org.apache.pulsar:pulsar-broker:2.10.4`
☕Maven	`org.apache.pulsar:pulsar-broker`	≥ 2.11.0&&< 2.11.1	2.11.1`org.apache.pulsar:pulsar-broker:2.11.1`

Affected Products

1 product · 5 configurations

Application

pulsarapache

≥ 2.10.0 && ≤ 2.10.3

1 version

2.11.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.pulsar:pulsar-broker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.pulsar:pulsar-broker to 2.10.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-47r2-phr8-m8cp is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-47r2-phr8-m8cp in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

CWE Classification

CWE-287Improper Authentication

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

pulsar

7.0/10

Code-Review10/10

Maintained10/10

Branch-ProtectionN/A

Assessed Sep 21, 2026

Timeline

Disclosed

Jul 12, 2023

Last updated

Feb 16, 2024

Identifiers

GHSA-47r2-phr8-m8cp

References

Advisorynvd.nist.gov Weblists.apache.org Packagegithub.com

Related vulnerabilities

Also affects pulsar-broker

This CVE is medium severity; 6 of 6 other CVEs affecting pulsar-broker are rated as high or higher (top: high).

CVE-2024-29834CVE-2024-28098CVE-2023-31007CVE-2023-30428CVE-2022-33683CVE-2022-33682

Same weakness: CWE-287

This CVE is medium severity; 1 of 2 other CVEs with CWE-287 is rated as high or higher (top: critical).

CVE-2026-63472CVE-2026-85716Browse all CWE-287

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

GHSA-47r2-phr8-m8cp — pulsar-broker

Exploitation Status

No confirmed exploitation observed yet

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

Frequently Asked Questions

Is GHSA-47r2-phr8-m8cp in your dependencies?