Is CVE-2026-42602 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-42602 being exploited in the wild.

How severe is CVE-2026-42602?

High severity, with a CVSS score of 8.1, published 13 May 2026.

Which products and versions are affected?

github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension (Go) >= 0.124.0, = 0.124.0, <= 0.150.0, 0.124.0 to 0.150.0.

Is there a fix for CVE-2026-42602?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-42602 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-42602?

Check whether you run github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension (Go), Opentelemetry Azure Authentication Extension, Opentelemetry Collector Contrib or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-42602: OpenTelemetry azureauthextension authentication bypass via token replay

Q: Is there a fix for CVE-2026-42602?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-42602 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-42602?

Check whether you run github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension (Go), Opentelemetry Azure Authentication Extension, Opentelemetry Collector Contrib or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-42602 · Severity: high · CVSS 8.1 · Published 2026-05-13

The Azure Authenticator Extension for OpenTelemetry, which is used to secure data collection pipelines, contains a flaw that allows unauthorized users to bypass security checks. By presenting a valid Azure token intended for a different service (like Key Vault or Storage), an attacker can trick the collector into accepting unauthorized data. This could lead to the injection of fraudulent monitoring data or unauthorized access to telemetry pipelines, potentially masking malicious activity or disrupting operations.

Vendors: Go, Opentelemetry.

Quick answers

Is CVE-2026-42602 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-42602 being exploited in the wild.
How severe is CVE-2026-42602?: High severity, with a CVSS score of 8.1, published 13 May 2026.
Which products and versions are affected?: github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension (Go) >= 0.124.0, <= 0.150.0, SEMVER:introduced=0.124.0, SEMVER:introduced=0.124.0,last_affected=0.150.0; Opentelemetry Azure Authentication Extension 0.124.0 to 0.150.0; Opentelemetry Collector Contrib >= 0.124.0, <= 0.150.0, 0.124.0 to 0.150.0.
Is there a fix for CVE-2026-42602?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-42602 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-42602?: Check whether you run github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension (Go), Opentelemetry Azure Authentication Extension, Opentelemetry Collector Contrib or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in the 'Authenticate' method of the azureauthextension (v0.124.0–v0.150.0) allows authentication bypass via token replay and scope confusion. The extension fails to perform standard JWT validation (signature, issuer, audience, or expiration checks); instead, it requests its own token for a scope derived from the client-supplied 'Host' header and performs a simple string comparison. An attacker with a valid Azure access token for any resource the collector's service principal can access (e.g., ARM, Graph, Key Vault) can authenticate by matching the 'Host' header to that resource's scope. This allows for the replay of existing tokens and the use of tokens minted for unrelated Azure services to gain access to the OpenTelemetry receiver.

Affected products

OpenTelemetry opentelemetry-collector-contrib/extension/azureauthextension 0.124.0 to 0.150.0

Identifiers

CVE-2026-42602
GHSA-pjv4-3c63-699f
GO-2026-5544

Timeline

2026-04-29: advisory: GitHub Security Advisory published
2026-05-13: disclosed: CVE-2026-42602 published to NVD

References

https://github.com/open-telemetry/opentelemetry-collector-contrib/security/advisories/GHSA-pjv4-3c63-699f

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.