Medium · CVSS 6.5CVE-2026-62147

Tempo-operator: tempo operator: query rbac bypassCVE-2026-62147

Answer in brief

CVE-2026-62147 records a Medium severity (CVSS 6.5) vulnerability in Tempo-operator: tempo operator: query rbac bypass. The current sources do not mark it as known exploited. The current feed maps Red Hat/rhosdt/tempo-operator-bundle (generic), Red Hat/rhosdt/tempo-rhel9-operator (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 13, 2026Updated Oct 31, 2026Source checked Nov 5, 2026First seen by HOL Jul 13, 2026Material review Oct 31, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.5
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Not reported

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Red Hat/rhosdt/tempo-operator-bundle (generic), Red Hat/rhosdt/tempo-rhel9-operator (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Red Hat/rhosdt/tempo-operator-bundlegeneric	*	Not reported
Red Hat/rhosdt/tempo-rhel9-operatorgeneric	*	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Red Hat/rhosdt/tempo-operator-bundle, Red Hat/rhosdt/tempo-rhel9-operator.
Review the reported fix. Source-reported workaround: There is no mitigation or workaround other than upgrading to tempo-operator.v0.21.0-2 (or later); until upgraded, administrators requiring strict namespace isolation of trace data should not rely on query RBAC alone and should consider restricting access to the Tempo query API at the network/route level as a temporary compensating control.

Evidence timeline and material changes

Published upstream
Jul 13, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 31, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 13, 2026

Sources and claim methodology

Upstream source description

The Tempo Operator's gateway component failed to consistently apply namespace-scoped redaction on some query API response paths when query RBAC was enabled, allowing an authenticated user to read span attributes belonging to other tenants' namespaces.

Quoted source text, attributed separately from HOL analysis.

Affected scope and exposure questions

The current feed maps Red Hat/rhosdt/tempo-operator-bundle (generic), Red Hat/rhosdt/tempo-rhel9-operator (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Red Hat/rhosdt/tempo-operator-bundlegeneric	*	Not reported
Red Hat/rhosdt/tempo-rhel9-operatorgeneric	*	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Red Hat/rhosdt/tempo-operator-bundle, Red Hat/rhosdt/tempo-rhel9-operator.

Review the reported fix. Source-reported workaround: There is no mitigation or workaround other than upgrading to tempo-operator.v0.21.0-2 (or later); until upgraded, administrators requiring strict namespace isolation of trace data should not rely on query RBAC alone and should consider restricting access to the Tempo query API at the network/route level as a temporary compensating control.

Sources and claim methodology

Upstream source description

Quoted source text, attributed separately from HOL analysis.