How severe is GHSA-cqgj-h8vf-4w59?

GHSA-cqgj-h8vf-4w59 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-cqgj-h8vf-4w59?

GHSA-cqgj-h8vf-4w59 affects the following packages: org.cometd.java:cometd-java-server-common (Maven), org.cometd.java:cometd-java-server-common (Maven), org.cometd.java:cometd-java-server-common (Maven), org.cometd.java:cometd-java-server-common (Maven). Ecosystems affected: Maven.

How do I fix GHSA-cqgj-h8vf-4w59?

Update org.cometd.java:cometd-java-server-common to 5.0.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cqgj-h8vf-4w59 is resolved across your whole dependency graph.

How do I detect GHSA-cqgj-h8vf-4w59 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-server-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cqgj-h8vf-4w59 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 GHSA-cqgj-h8vf-4w59 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cqgj-h8vf-4w59 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-cqgj-h8vf-4w59?

GHSA-cqgj-h8vf-4w59 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th 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-cqgj-h8vf-4w59?

GHSA-cqgj-h8vf-4w59 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cqgj-h8vf-4w59 published, and has it been updated?

GHSA-cqgj-h8vf-4w59 was published on June 10, 2026 and was last updated on June 10, 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

Acknowledgement extension out of memoryGHSA-cqgj-h8vf-4w59

HIGHFix: cometd/cometd#2118

GHSA-cqgj-h8vf-4w59 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.cometd.java:cometd-java-server-common. A fix is available for org.cometd.java:cometd-java-server-common — see the affected versions and patch details below.

Also known asCVE-2025-53114

Published

Jun 10, 2026

Updated

Jun 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-cqgj-h8vf-4w59.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% 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

4 pkgs affected

☕org.cometd.java:cometd-java-server-common☕org.cometd.java:cometd-java-server-common☕org.cometd.java:cometd-java-server-common☕org.cometd.java:cometd-java-server-common

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

Bad clients that always send a fixed batch value while the server is using the acknowledgement extension can cause the unacknowledged message queue to grow indefinitely, eventually resulting in an OutOfMemoryError.

Such bad clients would always send:

{
  "channel": "/meta/connect",
  ...
  "ext": { "ack": 1 }
}

The server would never clear the unacknowledged message queue, and one bad client can cause a server outage.

Patches

5.0.x - https://github.com/cometd/cometd/pull/2168 6.0.x - https://github.com/cometd/cometd/pull/2169 8.0.x - https://github.com/cometd/cometd/pull/2118

Workarounds

Disable the acknowledgement extension.

Resources

https://github.com/cometd/cometd/discussions/2116 https://github.com/cometd/cometd/issues/2117

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.cometd.java:cometd-java-server-common`	≥ 5.0.0&&< 5.0.23	5.0.23`org.cometd.java:cometd-java-server-common:5.0.23`
☕Maven	`org.cometd.java:cometd-java-server-common`	≥ 6.0.0&&< 6.0.19	6.0.19`org.cometd.java:cometd-java-server-common:6.0.19`
☕Maven	`org.cometd.java:cometd-java-server-common`	≥ 7.0.0&&< 7.0.19	7.0.19`org.cometd.java:cometd-java-server-common:7.0.19`
☕Maven	`org.cometd.java:cometd-java-server-common`	≥ 8.0.0&&< 8.0.9	8.0.9`org.cometd.java:cometd-java-server-common:8.0.9`

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-server-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.cometd.java:cometd-java-server-common to 5.0.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cqgj-h8vf-4w59 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

### Impact Bad clients that always send a fixed batch value while the server is using the acknowledgement extension can cause the unacknowledged message queue to grow indefinitely, eventually resulting in an OutOfMemoryError. Such bad clients would always send: ```json { "channel": "/meta/connect", ... "ext": { "ack": 1 } } ``` The server would never clear the unacknowledged message queue, and one bad client can cause a server outage. ### Patches 5.0.x - https://github.com/cometd/cometd/pull/2168 6.0.x - https://github.com/cometd/cometd/pull/2169 8.0.x - https://github.com/cometd/com