https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-15T20:07:05.383543+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-328574 EUVD-2026-328574 2026-10-15T20:07:05.428626+00:00 EUVD-2026-328574 https://cve.radiocsirt.org/vuln/fkie_cve-2025-53114 fkie_cve-2025-53114 2026-10-15T20:07:05.428668+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-cqgj-h8vf-4w59 GHSA-cqgj-h8vf-4w59 — Acknowledgement extension out of memory 2026-10-15T20:07:05.428718+00:00

Affected: Maven: org.cometd.java:cometd-java-server-common

### 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/cometd/pull/2118

### Workarounds Disable the acknowledgement extension.

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