How severe is CVE-2022-24280?

CVE-2022-24280 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 CVE-2022-24280?

CVE-2022-24280 affects the following packages: org.apache.pulsar:pulsar (Maven), org.apache.pulsar:pulsar (Maven), org.apache.pulsar:pulsar (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-24280?

Update org.apache.pulsar:pulsar to 2.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24280 is resolved across your whole dependency graph.

How do I detect CVE-2022-24280 in my Maven dependencies?

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

How do I mitigate CVE-2022-24280 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-24280 actively exploited in the wild?

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

CVE-2022-24280 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 73th 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-2022-24280?

CVE-2022-24280 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-24280 published, and has it been updated?

CVE-2022-24280 was published on September 23, 2022 and was last updated on October 28, 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

MEDIUM severity

CVE-2022-24280 — pulsar

MEDIUM

CVE-2022-24280 is a medium-severity (CVSS 6.5) Improper Input Validation vulnerability in org.apache.pulsar:pulsar. A fix is available for org.apache.pulsar:pulsar — see the affected versions and patch details below.

Apache Pulsar Proxy target broker address isn't validated

Also known asGHSA-3mg9-m3f6-v7fq

Published

Sep 23, 2022

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 3, 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-2022-24280.

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

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

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 Input Validation vulnerability in Proxy component of Apache Pulsar allows an attacker to make TCP/IP connection attempts that originate from the Pulsar Proxy's IP address. When the Apache Pulsar Proxy component is used, it is possible to attempt to open TCP/IP connections to any IP address and port that the Pulsar Proxy can connect to. An attacker could use this as a way for DoS attacks that originate from the Pulsar Proxy's IP address. It hasn’t been detected that the Pulsar Proxy authentication can be bypassed. The attacker will have to have a valid token to a properly secured Pulsar Proxy. This issue affects Apache Pulsar Proxy versions 2.7.0 to 2.7.4; 2.8.0 to 2.8.2; 2.9.0 to 2.9.1; 2.6.4 and earlier.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.pulsar:pulsar`	all versions	2.7.5`org.apache.pulsar:pulsar:2.7.5`
☕Maven	`org.apache.pulsar:pulsar`	≥ 2.8.0&&< 2.8.3	2.8.3`org.apache.pulsar:pulsar:2.8.3`
☕Maven	`org.apache.pulsar:pulsar`	≥ 2.9.0&&< 2.9.2	2.9.2`org.apache.pulsar:pulsar:2.9.2`

Affected Products

1 product · 4 configurations

Application

pulsarapache

≥ 2.9.0 && ≤ 2.6.4

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.pulsar:pulsar to 2.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24280 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-24280 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

None

Availability

High

Raw vector

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

CWE Classification

CWE-20Improper Input Validation

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Sep 23, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-24280

GHSA-3mg9-m3f6-v7fq

References

Advisorygithub.com · CVE 2022 24280.json Advisorynvd.nist.gov · CVE 2022 24280 Weblists.apache.org · ghs9jtjfbpy4c6xcftyvkl6swznlom1v Webgithub.com · CVE 2022 24280 Packagegithub.com · pulsar

Related vulnerabilities

Also affects pulsar

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

CVE-2023-30429CVE-2021-41571CVE-2021-22160

Same weakness: CWE-20

This CVE is medium severity; 4 of 5 other CVEs with CWE-20 are rated as high or higher (top: critical).

CVE-2026-62662GHSA-fmc8-p6q7-75ccGHSA-pjff-c2wc-f6jmCVE-2026-44265CVE-2026-119280Browse all CWE-20

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-24280 — pulsar

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 CVE-2022-24280 in your dependencies?