CVE-2026-42602

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
—
EPSS
12.8%
KEV
Not listed

Published

May 13, 2026

Last Modified

June 1, 2026

Advisory Details (1)

Auto-updated May 13, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

azureauthextension Authenticate method does not validate bearer tokens, allowing auth bypass via replay · Advisory · open-telemetry/opentelemetry-collector-contrib · GitHub

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
gogithub.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/open-telemetry/opentelemetry-collector-contrib/extension/azureauthextension———

Weakness Classification(5)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 117 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-18 02:29 UTCOSV refresh
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-13 22:30 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-08 15:15 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-06-30 23:22 UTCEPSS rescore
Show 75 more
  1. 2026-06-29 22:11 UTCGHSA enrichment
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 12:47 UTCGHSA enrichment
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 23:18 UTCGHSA enrichment
  7. 2026-06-27 09:17 UTCGHSA enrichment
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-26 20:27 UTCGHSA enrichment
  10. 2026-06-25 19:34 UTCGHSA enrichment
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-25 13:49 UTCEPSS rescore
  13. 2026-06-24 14:05 UTCEPSS rescore
  14. 2026-06-23 21:33 UTCEPSS rescore
  15. 2026-06-22 14:25 UTCEPSS rescore
  16. 2026-06-22 14:25 UTCEPSS rescore
  17. 2026-06-21 14:56 UTCEPSS rescore
  18. 2026-06-21 14:56 UTCEPSS rescore
  19. 2026-06-21 01:59 UTCEPSS rescore
  20. 2026-06-19 19:25 UTCEPSS rescore
  21. 2026-06-17 17:53 UTCEPSS rescore
  22. 2026-06-17 14:19 UTCGHSA enrichment
  23. 2026-06-16 22:27 UTCGHSA enrichment
  24. 2026-06-16 17:52 UTCEPSS rescore
  25. 2026-06-16 00:33 UTCGHSA enrichment
  26. 2026-06-15 17:49 UTCEPSS rescore
  27. 2026-06-15 01:17 UTCGHSA enrichment
  28. 2026-06-14 12:29 UTCGHSA enrichment
  29. 2026-06-13 23:41 UTCGHSA enrichment
  30. 2026-06-13 23:00 UTCEPSS rescore
  31. 2026-06-13 02:38 UTCGHSA enrichment
  32. 2026-06-12 23:12 UTCEPSS rescore
  33. 2026-06-12 23:12 UTCEPSS rescore
  34. 2026-06-12 13:47 UTCGHSA enrichment
  35. 2026-06-12 00:59 UTCGHSA enrichment
  36. 2026-06-11 14:00 UTCEPSS rescore
  37. 2026-06-11 12:12 UTCGHSA enrichment
  38. 2026-06-10 23:23 UTCGHSA enrichment
  39. 2026-06-10 22:18 UTCEPSS rescore
  40. 2026-06-10 13:22 UTCEPSS rescore
  41. 2026-06-10 13:22 UTCEPSS rescore
  42. 2026-06-10 10:35 UTCGHSA enrichment
  43. 2026-06-09 21:48 UTCGHSA enrichment
  44. 2026-06-09 08:48 UTCGHSA enrichment
  45. 2026-06-08 19:58 UTCGHSA enrichment
  46. 2026-06-08 14:17 UTCEPSS rescore
  47. 2026-06-08 14:17 UTCEPSS rescore
  48. 2026-06-08 04:55 UTCGHSA enrichment
  49. 2026-06-07 16:08 UTCGHSA enrichment
  50. 2026-06-07 15:25 UTCEPSS rescore
  51. 2026-06-07 15:25 UTCEPSS rescore
  52. 2026-06-07 03:20 UTCGHSA enrichment
  53. 2026-06-06 14:32 UTCGHSA enrichment
  54. 2026-06-06 13:47 UTCEPSS rescore
  55. 2026-06-06 13:47 UTCEPSS rescore
  56. 2026-06-06 01:44 UTCGHSA enrichment
  57. 2026-06-05 22:47 UTCEPSS rescore
  58. 2026-06-05 12:57 UTCGHSA enrichment
  59. 2026-06-05 06:10 UTCEPSS rescore
  60. 2026-06-05 06:10 UTCEPSS rescore
  61. 2026-06-05 00:09 UTCGHSA enrichment
  62. 2026-06-04 13:12 UTCEPSS rescore
  63. 2026-06-04 13:12 UTCEPSS rescore
  64. 2026-06-04 10:46 UTCGHSA enrichment
  65. 2026-06-03 21:58 UTCGHSA enrichment
  66. 2026-06-03 09:10 UTCGHSA enrichment
  67. 2026-06-02 20:22 UTCGHSA enrichment
  68. 2026-06-02 20:13 UTCEPSS rescore
  69. 2026-06-02 07:34 UTCGHSA enrichment
  70. 2026-06-01 18:46 UTCGHSA enrichment
  71. 2026-06-01 13:52 UTCEPSS rescore
  72. 2026-06-01 13:52 UTCEPSS rescore
  73. 2026-06-01 05:58 UTCGHSA enrichment
  74. 2026-05-31 22:30 UTCEPSS rescore
  75. 2026-05-31 22:30 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-42602?
CVE-2026-42602 is a high vulnerability published on May 13, 2026. 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…
When was CVE-2026-42602 disclosed?
CVE-2026-42602 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42602 actively exploited?
CVE-2026-42602 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42602?
CVE-2026-42602 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-42602?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42602, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42602

Explore →

Is Your Infrastructure Affected by CVE-2026-42602?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs