Skip to content
Fencer Intel
high 7.5

CVE-2025-53114 json

CometD has acknowledgement extension out of memory

published 4mo ago modified 28d ago also EUVD-2025-210284 , GHSA-cqgj-h8vf-4w59

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

CometD is a scalable comet implementation for web messaging. In versions 5.0.0 through 5.0.22, 6.0.0 through 6.0.18, 7.0.0 through 7.0.18, and 8.0.0 through 8.0.8, bad clients that always send a fixed batch value when the server is using the acknowledgement extension may cause the unacknowledged message queue to grow indefinitely, eventually causing an `OutOfMemoryError`. Versions 5.0.23, 6.0.19, 7.0.19, and 8.0.9 patch the issue. As a workaround, disable the acknowledgement extension.

Patch / fix

  • maven org.cometd.java:cometd-java-server-common 5.0.23, 6.0.19, 7.0.19, 8.0.9
  • cometd cometd 5.0.23, 6.0.19, 7.0.19, 8.0.9
  • org.cometd.java cometd-java-server-common 5.0.23, 6.0.19, 7.0.19, 8.0.9

Is CVE-2025-53114 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
4mo ago

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.cometd.java:cometd-java-server-common
>=5.0.0, <5.0.23
>=6.0.0, <6.0.19
>=7.0.0, <7.0.19
>=8.0.0, <8.0.9
5.0.23
6.0.19
7.0.19
8.0.9

Affected products

  • cometd cometd

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.