Skip to main content
← All vulnerabilities
CVE-2026-42602GO-2026-5544GHSA-PJV4-3C63-699F

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

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 0.151.0
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: partial

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).

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • open-telemetry opentelemetry-collector-contrib

    From 0.124.0 · through 0.150.0

  • github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextensionGo

    From 0.124.0 · fixed in 0.151.0

  • github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextensionGo

    From 0.124.0 · through 0.150.0

References 1

GitHub · open-telemetry/opentelemetry-collector-contrib