GPU VulnDB

Database/Control plane, storage & DevOps

Prometheus: remote_write follows 3xx redirects with the bearer token attached, leaking cloud credentials

CVSS 6.3CVE-2026-119566Control plane, storage & DevOpscurated

Impact

Prometheus through 3.15.1 replays its Azure AD or Google IAM bearer token when a remote_write request is redirected, so whoever controls the remote-write endpoint - or any host that can return a 3xx in that path - captures a working cloud token. The token is the one the monitoring stack uses to write to the metrics backend, so an attacker can at minimum forge or poison metrics for the whole fleet, and the blast radius is whatever else that identity is granted. For a GPU operator this is the credential behind DCGM, node-exporter and job-level telemetry across the cluster: poisoned or deleted metrics break capacity accounting, thermal and XID alerting, and the autoscaling and eviction decisions built on them. Exploitation requires the attacker to be in a position to control or redirect the remote-write destination, which is why the score is moderate.

Who can reach it

Network. An attacker who controls the configured remote-write endpoint, or an intermediary able to answer those requests with a redirect, captures the token. No authentication to Prometheus itself is required - the victim is Prometheus's outbound write path.

What to do

Upgrade Prometheus once a release carrying the prometheus/common fix (PR 901) ships; no fixed Prometheus version is named in the record, so track that PR rather than assume a version. Mitigate now: pin remote_write to endpoints you control over TLS with certificate validation, disable or constrain redirect following at the egress proxy, and scope the Azure AD / Google IAM identity to metric writes only. Applying the fix is a Prometheus restart, not a node action; rotate the bearer-token identity if you believe a redirect was ever followed.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.