Authenticated telemetry injection via bearer-token replay
Published May 13, 2026 · Updated May 13, 2026
Authentication bypass in OpenTelemetry Collector Contrib 0.124.0 through 0.150.0 allows remote authenticated users to inject telemetry. The azureauthextension Authenticate method compares the bearer token with a token minted for a scope derived from the client-supplied Host header instead of verifying the JWT signature, issuer, audience, and lifetime. Exploitation requires a valid Azure token issued to the collector identity and receiver-side azure_auth configuration, enabling forged traces, metrics, or logs to poison downstream observability data.
Summary
What happened
Authentication bypass in OpenTelemetry Collector Contrib 0.124.0 through 0.150.0 allows remote authenticated users to inject telemetry. The azureauthextension Authenticate method compares the bearer token with a token minted for a scope derived from the client-supplied Host header instead of verifying the JWT signature, issuer, audience, and lifetime. Exploitation requires a valid Azure token issued to the collector identity and receiver-side azure_auth configuration, enabling forged traces, metrics, or logs to poison downstream observability data.
The record
- CVE
- CVE-2026-42602
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- OpenTelemetry
- Product
- OpenTelemetry Collector Contrib
- Classifications
- CWE-347, CWE-208, CWE-294, CWE-287, CWE-290, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.124.0, <= 0.150.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA bearer-token replay proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo