How severe is CVE-2022-24721?

CVE-2022-24721 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-24721?

CVE-2022-24721 affects the following packages: org.cometd.java:cometd-java-oort (Maven), org.cometd.java:cometd-java-oort (Maven), org.cometd.java:cometd-java-oort (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-24721?

Update org.cometd.java:cometd-java-oort to 5.0.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24721 is resolved across your whole dependency graph.

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

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

How do I mitigate CVE-2022-24721 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 CVE-2022-24721 actively exploited in the wild?

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

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

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

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

CVE-2022-24721 was published on March 15, 2022 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

HIGH severity

CVE-2022-24721 — cometd-java-oort

HIGHFix: cometd/cometd@bb445a1

CVE-2022-24721 is a high-severity (CVSS 8.1) CWE-863 vulnerability in org.cometd.java:cometd-java-oort. A fix is available for org.cometd.java:cometd-java-oort — see the affected versions and patch details below.

Incorrect Authorization in org.cometd.oort

Also known asGHSA-rjmq-6v55-4rjv

Published

Mar 15, 2022

Updated

Aug 12, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-24721.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2022-24721 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

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

Real-World Exposure

3 pkgs affected

☕org.cometd.java:cometd-java-oort☕org.cometd.java:cometd-java-oort☕org.cometd.java:cometd-java-oort

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

Impact

Internal usage of Oort and Seti channels is improperly authorized, so any remote user could subscribe and publish to those channels. By subscribing to those channels, a remote user may be able to watch cluster-internal traffic that contains other user's (possibly sensitive) data. By publishing to those channels, a remote user may be able to create/modify/delete other user's data and modify the cluster structure. The issue impacts any version up to 5.0.10, 6.0.5 and 7.0.5.

Patches

The issue has been fixed in 5.0.11, 6.0.6 and 7.0.6.

Workarounds

The workaround is to install a custom SecurityPolicy that forbids subscription and publishing to remote, non-Oort, sessions on Oort and Seti channels. This workaround could be implemented in any affected version.

References

cometd/cometd#1146

For more information

If you have any questions or comments about this advisory:

Email us at [email protected]

Credits

https://www.redteam-pentesting.de/

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.cometd.java:cometd-java-oort`	all versions	5.0.11`org.cometd.java:cometd-java-oort:5.0.11`
☕Maven	`org.cometd.java:cometd-java-oort`	≥ 6.0.0&&< 6.0.6	6.0.6`org.cometd.java:cometd-java-oort:6.0.6`
☕Maven	`org.cometd.java:cometd-java-oort`	≥ 7.0.0&&< 7.0.6	7.0.6`org.cometd.java:cometd-java-oort:7.0.6`

Affected Products

1 product · 3 configurations

Application

cometdcometd

≥ 7.0.0 && < 7.0.6

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.cometd.java:cometd-java-oort, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.cometd.java:cometd-java-oort to 5.0.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24721 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

### Impact Internal usage of Oort and Seti channels is improperly authorized, so any remote user could subscribe and publish to those channels. By subscribing to those channels, a remote user may be able to watch cluster-internal traffic that contains other user's (possibly sensitive) data. By publishing to those channels, a remote user may be able to create/modify/delete other user's data and modify the cluster structure. The issue impacts any version up to 5.0.10, 6.0.5 and 7.0.5. ### Patches The issue has been fixed in 5.0.11, 6.0.6 and 7.0.6. ### Workarounds The workaround is to install