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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2025-2842: 0.40% estimated exploitation activity in the next 30 days; percentile 34.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A flaw was found in the Tempo Operator. When the Jaeger UI Monitor Tab functionality is enabled in a Tempo instance managed by the Tempo Operator, the Operator creates a ClusterRoleBinding for the Service Account of the Tempo instance to grant the cluster-monitoring-view ClusterRole. This can be exploited if a user has 'create' permissions on TempoStack and 'get' permissions on Secret in a namespace (for example, a user has ClusterAdmin permissions for a specific namespace), as the user can read the token of the Tempo service account and therefore has access to see all cluster metrics.

Published by the source

2 Apr 2025, 15:31 UTC

Last modified by the source

11 May 2026, 13:53 UTC

Source last checked

26 Oct 2026, 15:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5xf3-gmx4-529v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-2842

Advisory: Grafana Tempo Operator Vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
IDs: CVE-2025-2842, GHSA-5xf3-gmx4-529v
Record: https://patchnext.com/advisories/cve-2025-2842 (revision 1, source checked 26 Oct 2026, 15:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/grafana/tempo-operator 0.16.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/grafana/tempo-operator: affected < 0.16.0; fixed in 0.16.0

## Suggested inspection (read-only)
- Go github.com/grafana/tempo-operator: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/grafana/tempo-operator.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5xf3-gmx4-529v (GitHub-reviewed advisory GHSA-5xf3-gmx4-529v lists affected ranges: Go github.com/grafana/tempo-operator >=0 <0.16.0)

Commands are suggestions: review each one before running it.