Approved changes feed: RSS · Atom
cpe:2.3:a:cometd:cometd:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Cometd (a37ad8ae-03fc-5ea6-839c-2dc42706e9c1) |
|---|---|
| Product | Cometd (d6ca010a-2742-5d53-a93d-db87f22489dc) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/cometd/cometd |
purl2cpe | 2026-06-01 10:11:27.848629 |
pkg:maven/org.cometd/cometd-project |
purl2cpe | 2026-06-01 10:11:27.848632 |
pkg:npm/cometd |
purl2cpe | 2026-06-01 10:11:27.848635 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-53114 |
vulnerable | 2026-07-28 23:58:38.354553 |
CometD has acknowledgement extension out of memory
HIGH (7.5)
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.
Published: 2026-06-18T16:25:47.388Z
Updated: 2026-06-18T17:33:39.552Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-24721 |
vulnerable | 2026-06-08 05:41:01.432253 |
Incorrect Authorization in org.cometd.oort
HIGH (8.1)
CometD is a scalable comet implementation for web messaging. In any version prior to 5.0.11, 6.0.6, and 7.0.6, 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 users' (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. A fix is available in versions 5.0.11, 6.0.6, and 7.0.6. As a workaround, install a custom `SecurityPolicy` that forbids subscription and publishing to remote, non-Oort, sessions on Oort and Seti channels.
Published: 2022-03-15T13:45:13.000Z
Updated: 2025-04-23T18:53:56.693Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.