Skip to content
Fencer Vulns
high 7.7

CVE-2026-75889 json

CVE-2026-75889 CVE Record

published 2026-08-27 2 mo ago modified 2026-09-02 2 mo ago also BIT-grafana-alloy-2026-75889 , EUVD-2026-67162

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami grafana-alloy 1.19.0
  • alloy SLES for SAP applications 16.0, SLES 16.0 1.19.2-160000.1.1
  • alloy SLE Module for Basesystem 15 SP7 1.19.2-150700.15.29.1

suse advisories SUSE-SU-2026:24148-1SUSE-SU-2026:4408-1

  • alloy openSUSE Leap 16.0 1.19.2-160000.1.1
  • alloy openSUSE Tumbleweed 1.19.2-1.1

opensuse advisories openSUSE-SU-2026:22032-1openSUSE-SU-2026:11803-1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OSV 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami grafana-alloy
>=1.0.0, <1.19.0
1.19.0

Affected products

  • Grafana Alloy

Classification

Weakness
  • CWE-552 Files or Directories Accessible to External Parties

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.