← Back
CVE-2026-42348
medium
CVSS 5.9
Vulnerability in OpenTelemetry.OpAmp.Client (CVE-2026-42348)
Summary
vulnerability in OpenTelemetry.OpAmp.Client (CVE-2026-42348). Risk of unauthorized operations or information disclosure. Exploitable via ``ReadAsByteArrayAsync``. Mitigation: upgrade to `0.2.0-alpha.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42348** has been found in OpenTelemetry.OpAmp.Client.
Attackers can target a specific entry point like ``ReadAsByteArrayAsync`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.9/10.
What to do: upgrade OpenTelemetry.OpAmp.Client to **0.2.0-alpha.1** or later.
If unsure, ask your IT team or search "OpenTelemetry.OpAmp.Client CVE-2026-42348" on the vendor's site.
CVE-2026-42348 (OpenTelemetry.OpAmp.Client) — CWE-789 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `ReadAsByteArrayAsync` / `HttpResponseMessage.Content`
Patched: `0.2.0-alpha.1` — 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-789) exists in OpenTelemetry.OpAmp.Client. Attackers reach the vulnerable code path via ``ReadAsByteArrayAsync`` without authentication.
📍 Affected scope
OpenTelemetry.OpAmp.Client — . Attack surface: `ReadAsByteArrayAsync` / `HttpResponseMessage.Content`.
🔥 Severity
Severity: Medium (CVSS 5.9/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.2.0-alpha.1**.
🛡️ 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 'OpenTelemetry.OpAmp.Client' .` 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 'OpenTelemetry.OpAmp.Client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `OpenTelemetry.OpAmp.Client` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade OpenTelemetry.OpAmp.Client to 0.2.0-alpha.1ステージング環境で 0.2.0-alpha.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
nuget
OpenTelemetry.OpAmp.Client
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.2.0-alpha.1"}]}]