Categories
CVE-2026-42602 high CVSS 8.1

Vulnerability in github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension (CVE-2026-42602)

Summary

Vulnerability in github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension (CVE-2026-42602). Data can be tampered with by attackers. Exploitable via POST /v1/traces.

Original description

The description as published by the source.

Authenticate method auth bypass in github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension

Source: NIST National Vulnerability Database 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-2026-42602 has been found in github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension.
Attackers can target a specific entry point like POST /v1/traces over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension CVE-2026-42602" on the vendor's site.

CVE-2026-42602 (github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension) — CWE-208 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /v1/traces / azureauthextension / Authenticate / Host
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-208) exists in github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension. Attackers reach the vulnerable code path via POST /v1/traces.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension. Attack surface: POST /v1/traces / azureauthextension / Authenticate / Host.

🔥 Severity

Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 POST /v1/traces requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /v1/traces' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /v1/traces への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify
    Replay attack against POST /v1/traces on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension
[{"type":"SEMVER","events":[{"introduced":"0.124.0"},{"fixed":"0.151.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details