CVE-2026-42602: open-telemetry opentelemetry-collector-contrib · Timing Side Channel
Affects open-telemetry opentelemetry-collector-contribSource CVE Database V5
Not known to be exploited · CVSS 8.1 High · patch available : patch open-telemetry opentelemetry-collector-contrib soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| open-telemetryopentelemetry-collector-contrib | Affected
| Fixed in– |
AI-suggested
A patch is available for this vulnerability. Since the affected product is a cloud-hosted service, the vendor typically manages remediation server-side. Users should verify with the vendor advisory that their service version is updated beyond 0.150.0 or that the patch has been applied. Until then, avoid relying on vulnerable versions. No additional mitigation steps are specified in the provided data.
Description
A vulnerability in the azureauthextension component of opentelemetry-collector-contrib versions 0.124.0 through 0.150.0 allows server-side authentication bypass. The extension improperly validates Azure access tokens by comparing them as strings without proper JWT validation and uses the client-supplied Host header to determine token scope. This flaw enables an attacker holding any valid Azure token for any scope the collector's identity can mint to authenticate to any OpenTelemetry receiver using azure_auth. Tokens remain valid for their full lifetime, typically several hours. The vulnerability has a high severity with a CVSS score of 8.1.