# CVE-2026-119566: Prometheus through 3.15.1 Credential Leak via remote_write Cross-Host Redirects


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 30 Oct 2026
- **Updated:** 4 Nov 2026
- **Also known as:** AZL-112688, DEBIAN-CVE-2026-119566, GHSA-597x-6fqq-75wr, UBUNTU-CVE-2026-119566

## What is CVE-2026-119566?

CVE-2026-119566 is a medium-severity vulnerability in prometheus, published on 30 Oct 2026. 

### Official description

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.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-119566?


## How do I fix CVE-2026-119566?

Upgrade to a fixed version.

## Is CVE-2026-119566 being exploited?

There is no known exploitation of CVE-2026-119566 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119566 and fix it if it is affected.

What it is: CVE-2026-119566 is a medium-severity vulnerability in prometheus, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119566 in the wild and no public exploit code.

Affected product: prometheus. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119566/ (Markdown: https://insights.sbomify.com/CVE-2026-119566/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119566
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119566
- OSV: https://osv.dev/vulnerability/CVE-2026-119566

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119566/
Summaries are generated and may contain mistakes; the official description above is the record.