Advisory record · GHSA-5xf3-gmx4-529v

Grafana Tempo Operator Vulnerable to Exposure of Sensitive Information to an Unauthorized Actor

CVSS 4.3 MediumEPSS 0.0040 · 34th percentile

Published by the GitHub Advisory Database at 2 Apr 2025, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/grafana/tempo-operatorGo<0.16.00.16.0
Identifiers
GHSA-5xf3-gmx4-529v · CVE-2025-2842 · GO-2026-5161
Weakness (CWE)
CWE-200
Published
2 Apr 2025
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Grafana Tempo Operator versions before 0.16.0 are affected. When the Jaeger UI Monitor Tab is enabled on a Tempo instance, the Operator binds the instance's service account to the cluster-monitoring-view ClusterRole. A user with create permission on TempoStack and get permission on Secrets in a namespace can read that service account's token and so view all cluster metrics. Upgrade to version 0.16.0 or later.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.0040, the 34th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:07 UTC First seen by agentprime
  2. 31 Oct 2026, 15:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.