# Tempo-operator: tempo operator: query rbac bypass

CVE record · `CVE-2026-62147`

- **Identifiers:** `CVE-2026-62147`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **CNA:** redhat
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Technologies:** [Red Hat OpenShift distributed tracing 3.10.1](https://agentprime.io/advisories/technology/red-hat-openshift-distributed-tracing-3-10-1.md)
- **Published:** 13 Jul 2026
- **Updated:** 31 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: redhat) at 13 Jul 2026, 11:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Red Hat. Product: Red Hat OpenShift distributed tracing 3.10.1.
  - unaffected: `1782510941 to before *` (rpm)
  - Other versions: affected
  - Package name: `rhosdt/tempo-operator-bundle`
  - Collection: `https://catalog.redhat.com/software/containers/`
- Vendor: Red Hat. Product: Red Hat OpenShift distributed tracing 3.10.1.
  - unaffected: `1782501195 to before *` (rpm)
  - Other versions: affected
  - Package name: `rhosdt/tempo-rhel9-operator`
  - Collection: `https://catalog.redhat.com/software/containers/`

## Machine-written summary

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

> Red Hat OpenShift distributed tracing 3.10.1 (the Tempo Operator gateway) does not consistently apply namespace-scoped redaction on some query API responses when query RBAC is enabled. An authenticated user can read span attributes from other tenants' namespaces. Version data is unclear, and no clear fixed version is listed.

Written 13 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from CNA (redhat)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0040, the 35th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 13 Jul 2026, 11:43 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-62147)

## Sources

- [CVE List: CVE-2026-62147](https://www.cve.org/CVERecord?id=CVE-2026-62147)
- [NVD: CVE-2026-62147](https://nvd.nist.gov/vuln/detail/CVE-2026-62147)

### References from the CNA

- <https://access.redhat.com/errata/RHSA-2026:33612> (vendor-advisory, redhat)
- <https://access.redhat.com/security/cve/CVE-2026-62147> (vdb-entry, redhat)
- <https://bugzilla.redhat.com/show_bug.cgi?id=2499635> (issue-tracking, redhat)

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-62147>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-62147/>. Everything for agents: <https://agentprime.io/llms.txt>.
