Vulnerability in org.cometd.java:cometd-java-server-common (CVE-2025-53114)
Summary
Vulnerability in org.cometd.java:cometd-java-server-common (CVE-2025-53114). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.0.x or later.
Original description
The description as published by the source.
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
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-53114 has been found in org.cometd.java:cometd-java-server-common.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade org.cometd.java:cometd-java-server-common to 5.0.x or later.
If unsure, ask your IT team or search "org.cometd.java:cometd-java-server-common CVE-2025-53114" on the vendor's site.
CVE-2025-53114 (org.cometd.java:cometd-java-server-common) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.0.x — apply immediately
Workaround: Disable the acknowledgement extension.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in org.cometd.java:cometd-java-server-common.
Check the vendor advisory for the affected versions of org.cometd.java:cometd-java-server-common.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 5.0.x.
Workaround: Disable the acknowledgement extension.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.cometd.java:cometd-java-server-common を使っているサービスとバージョンを洗い出す。
-
2Apply temporary workaround mitigate
Disable the acknowledgement extension.パッチが適用されるまでの応急処置として、Disable the acknowledgement extension. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade org.cometd.java:cometd-java-server-common to 5.0.xステージング環境で 5.0.x に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。