Skip to content
Connect AISign inSign up free
CVE-2026-426028.1HighCWE-208

CVE-2026-42602: azureauthextension Authenticate method does not validate bearer tokens, allowing auth bypass via replay

open-telemetry · opentelemetry-collector-contrib

Affected: open-telemetry opentelemetry-collector-contrib · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.2%probability of exploitation in the next 30 days
12th percentile
050100

Higher than 12% of scored CVEs

8.1HighCVSS 3.1
LowHigh

DescriptionCVE.org

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

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • open-telemetry · opentelemetry-collector-contrib>= 0.124.0, <= 0.150.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
May 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-42602 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References