Prometheus through 3.15.1 contains a credential leak vulnerability that allows attackers to capture Azure AD or Google IAM bearer tokens by redirecting remote_write requests to another host. Attackers controlling the remote-write endpoint or a redirecting server can return a 3xx to their host and replay the token, for example to write metrics to the victim's backend.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/prometheus/common/pull/901 related, patch, issue-tracking
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.3 · prometheusNVD modified 2026-10-30 11:31
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 6
- https://github.com/prometheus/prometheus/blob/v3.15.1/storage/remote/azuread/azuread.go#L326-L333 technical-description
- https://github.com/prometheus/prometheus/blob/v3.15.1/storage/remote/client.go#L205-L216 technical-description
- https://github.com/prometheus/common/pull/901 related, patch, issue-tracking
- https://abraxaslabs.tech/research/prometheus-bearer-redirect third-party-advisory
- https://github.com/prometheus/prometheus product
- https://www.vulncheck.com/advisories/prometheus-through-3.15.1-credential-leak-via-remote-write-cross-host-redirects third-party-advisory