Read the docs
TI-2026-30882 Aliases CVE-2026-42602GHSA-pjv4-3c63-699f

azureauthextension Authenticate method does not validate bearer tokens, allowing auth bypass via replay

Priority HIGH 68CWE-208Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Information disclosure, Security bypass
Confidentiality · integrity · availability
None · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-208 and CWE-287.

Summary

azureauthextension is the Azure Authenticator Extension. From 0.124.0 to 0.150.0, a server-side authentication bypass in azureauthextension allows any party who holds a single valid Azure access token for any scope the collector's configured identity can mint for to authenticate to any OpenTelemetry receiver that uses auth: azure_auth. The extension's Authenticate method does not validate incoming bearer tokens as JWTs. Instead, it calls its own configured credential to obtain an access token and compares the client's token to the result with string equality — and the scope for that server-side token request is taken from the client-supplied Host header. As a result, a token minted for any Azure resource the service principal has ever been issued a token for (ARM, Graph, Key Vault, Storage, etc.) will authenticate to the collector if the attacker picks a matching Host. Tokens are replayable for the full issued lifetime (commonly several hours for managed identity tokens).

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00222 12th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
open-telemetryopentelemetry-collector-contrib0.124.0 – 0.150.0—No fix listedCNA
—github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension (Go)0.124.0 – 0.150.0—No fix listedGHSA-pjv4-3c63-699f
  • opentelemetry-collector-contrib Vendoropen-telemetry Affected 0.124.0 – 0.150.0 Fixed in — No fix listed CNA
  • github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension (Go) Vendor— Affected 0.124.0 – 0.150.0 Fixed in — No fix listed GHSA-pjv4-3c63-699f

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:opentelemetry:opentelemetry_collector_contrib:*:*:*:*:*:go:*:*0.124.0 – 0.150.0Vulnerableopen-telemetry
  • cpe:2.3:a:opentelemetry:opentelemetry_collector_contrib:*:*:*:*:*:go:*:* Versions 0.124.0 – 0.150.0 Vulnerable ·open-telemetry

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-42602
  2. 2026-10-03 Alias added: GHSA-pjv4-3c63-699f

References

Sources