# CVE-2026-75889: CVE-2026-75889 CVE Record

> Attackers with ServiceMonitor write access can read arbitrary local files via bearerTokenFile, potentially stealing Kubernetes service account tokens.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** BIT-grafana-alloy-2026-75889, GHSA-6vgr-r2fg-p38q

## What is CVE-2026-75889?

CVE-2026-75889 is a high-severity path traversal vulnerability in Grafana Alloy, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grafana Alloy’s prometheus.operator.servicemonitors component allows a user who can create or modify ServiceMonitor resources in a watched namespace to specify an arbitrary local file through bearerTokenFile. Alloy reads the file and sends its contents as a bearer token to an attacker-controlled scrape endpoint. This may disclose files accessible to the Alloy process, including its projected Kubernetes service account token, potentially granting the attacker Alloy’s Kubernetes permissions. Exploitation requires ServiceMonitor write access and lower privileges than Alloy’s service account.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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

1 open source package ship an affected version, including grafana-alloy.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `grafana-alloy` | Bitnami | From 1.0.0 | 1.19.0 |

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

Upgrade grafana-alloy to 1.19.0 or later.

## Is CVE-2026-75889 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75889 is a high-severity path traversal vulnerability in Grafana Alloy, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75889 in the wild and no public exploit code.

Affected packages and fixed versions:
- grafana-alloy (Bitnami): affected from 1.0.0; fixed in 1.19.0

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-75889/ (Markdown: https://insights.sbomify.com/CVE-2026-75889/index.md)
```

## Sources

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

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