← Back
CVE-2025-53114
high
CVSS 7.5
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-400) exists in org.cometd.java:cometd-java-server-common.
📍 Affected scope
org.cometd.java:cometd-java-server-common — .
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.0.x**.
🛡️ Workaround
Workaround: Disable the acknowledgement extension.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.cometd.java:cometd-java-server-common' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.cometd.java:cometd-java-server-common' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.cometd.java:cometd-java-server-common` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Disable the acknowledgement extension.パッチが適用されるまでの応急処置として、Disable the acknowledgement extension. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade org.cometd.java:cometd-java-server-common to 5.0.xステージング環境で 5.0.x に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.cometd.java:cometd-java-server-common
[{"type":"ECOSYSTEM","events":[{"introduced":"8.0.0"},{"fixed":"8.0.9"}]}]