CVE-2025-53114: CometD has acknowledgement extension out of memory
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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-53114 is a denial-of-service risk in CometD. If the acknowledgement extension is enabled, a misbehaving unauthenticated client can cause the server’s unacknowledged message queue to grow until memory is exhausted. This can crash or disrupt messaging services. Patched CometD releases are available.
Executive priority
Treat as a high-priority availability issue for systems relying on CometD messaging, especially public-facing services. The fix is available, and the workaround is clear. Prioritize based on exposure and business dependency on real-time messaging uptime.
Technical view
Affected CometD versions 5.0.0-5.0.22, 6.0.0-6.0.18, 7.0.0-7.0.18, and 8.0.0-8.0.8 mishandle clients that repeatedly send a fixed batch value when acknowledgement is enabled. The result is unbounded queue growth and potential OutOfMemoryError. CVSS 3.1 is 7.5: network, low complexity, unauthenticated, availability impact only.
Likely exposure
Exposure is likely where CometD servers run affected versions and use the acknowledgement extension. Internet-facing messaging endpoints have higher business risk because exploitation requires network access and no authentication according to the CVSS vector.
Exploitation context
The provided sources do not report active exploitation, and this CVE is not marked KEV. The issue is straightforward denial of service: a bad client behavior can exhaust server memory. No confidentiality or integrity impact is described.
Researcher notes
This is CWE-400 resource consumption in the acknowledgement extension path. The source bundle identifies patches and related pull requests but does not provide evidence of exploitation in the wild. Avoid assuming exposure unless acknowledgement is enabled and the deployed version is within the affected ranges.
Mitigation direction
Upgrade CometD to 5.0.23, 6.0.19, 7.0.19, or 8.0.9 as applicable.
If immediate upgrade is not possible, disable the acknowledgement extension as the documented workaround.
Monitor vendor advisory and related GitHub issue or pull requests for implementation details and updates.
Prioritize externally reachable CometD deployments and high-availability messaging services.
Validation and detection
Inventory applications and dependencies using CometD.
Identify deployed CometD versions and compare them with affected version ranges.
Confirm whether the acknowledgement extension is enabled on each CometD server.
Verify upgraded instances report a fixed CometD version.
Review logs and monitoring for memory growth or OutOfMemoryError events.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.