← Back
CVE-2026-54712
medium
CVSS 5.3
Vulnerability in io.opentelemetry.javaagent:opentelemetry-javaagent (CVE-2026-54712)
Summary
vulnerability in io.opentelemetry.javaagent:opentelemetry-javaagent (CVE-2026-54712). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.27.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54712** has been found in io.opentelemetry.javaagent:opentelemetry-javaagent.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade io.opentelemetry.javaagent:opentelemetry-javaagent to **2.27.0** or later.
If unsure, ask your IT team or search "io.opentelemetry.javaagent:opentelemetry-javaagent CVE-2026-54712" on the vendor's site.
CVE-2026-54712 (io.opentelemetry.javaagent:opentelemetry-javaagent) — CWE-400 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `2.27.0` — apply immediately
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 io.opentelemetry.javaagent:opentelemetry-javaagent.
📍 Affected scope
io.opentelemetry.javaagent:opentelemetry-javaagent — .
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.27.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'io.opentelemetry.javaagent:opentelemetry-javaagent' .` 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 'io.opentelemetry.javaagent:opentelemetry-javaagent' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.opentelemetry.javaagent:opentelemetry-javaagent` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade io.opentelemetry.javaagent:opentelemetry-javaagent to 2.27.0ステージング環境で 2.27.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.opentelemetry.javaagent:opentelemetry-javaagent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.27.0"}]}]
References
- web https://github.com/open-telemetry/opentelemetry-java-instrumentation/security/advisories/GHSA-fq3f-m5qm-99f5
- web https://nvd.nist.gov/vuln/detail/CVE-2026-54712
- web https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/17870
- web https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/6ef18806d5daa4913619e4cb33d2d7ed6a853c22
- web https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v2.27.0
- web https://github.com/advisories/GHSA-fq3f-m5qm-99f5