Insufficiently Protected Credentials Affecting github.com/prometheus/prometheus/storage/remote/azuread package, versions >=0.0.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-GITHUBCOMPROMETHEUSPROMETHEUSSTORAGEREMOTEAZUREAD-22113895
- published1 Nov 2026
- disclosed11 Oct 2026
- creditUnknown
Introduced: 11 Oct 2026
NewCVE-2026-119566 (opens in a new tab)How to fix?
There is no fixed version for github.com/prometheus/prometheus/storage/remote/azuread.
Overview
Affected versions of this package are vulnerable to Insufficiently Protected Credentials on cross-host redirects in the azureADRoundTripper.RoundTrip method (storage/remote/azuread/azuread.go) and the equivalent googleiam round-tripper, which call req.Header.Set("Authorization", "Bearer "+token) on every request. An attacker who controls or intercepts a configured remote_write endpoint can capture the Azure AD or GCP access token by answering with a redirect to a host they control, because storage/remote/client.go layers these round-trippers outside the redirect-aware transport so the token is reattached on each hop. This affects only remote_write configured with azuread: or google_iam:, neither of which is present in a default configuration.