CVE-2026-62147

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-07-13. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 13, 2026

Advisory Details (2)

Auto-updated Jul 13, 2026
Patch available. Sources: redhat.
redhat

2499635 – (CVE-2026-62147) CVE-2026-62147 tempo-operator: Tempo Operator: Query RBAC bypass

https://bugzilla.redhat.com/show_bug.cgi?id=2499635
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-62147

Vendor Advisories for CVE-2026-62147(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-30 16:28 UTCEPSS rescore
  2. 2026-07-30 14:21 UTCEG score recompute
  3. 2026-07-30 14:20 UTCGHSA enrichment
  4. 2026-07-30 01:30 UTCEPSS rescore
  5. 2026-07-30 01:30 UTCEPSS rescore
  6. 2026-07-29 13:43 UTCEG score recompute
  7. 2026-07-29 13:43 UTCGHSA enrichment
  8. 2026-07-28 15:37 UTCEPSS rescore
  9. 2026-07-28 13:07 UTCEG score recompute
  10. 2026-07-28 13:07 UTCGHSA enrichment
  11. 2026-07-27 14:14 UTCEPSS rescore
  12. 2026-07-27 12:29 UTCEG score recompute
  13. 2026-07-27 12:29 UTCGHSA enrichment
  14. 2026-07-26 14:54 UTCEPSS rescore
  15. 2026-07-26 14:54 UTCEPSS rescore
  16. 2026-07-26 11:53 UTCEG score recompute
  17. 2026-07-26 11:53 UTCGHSA enrichment
  18. 2026-07-25 14:18 UTCEPSS rescore
  19. 2026-07-25 14:18 UTCEPSS rescore
  20. 2026-07-24 14:18 UTCEPSS rescore
  21. 2026-07-24 14:18 UTCEPSS rescore
  22. 2026-07-23 14:18 UTCEPSS rescore
  23. 2026-07-23 14:18 UTCEPSS rescore
  24. 2026-07-23 03:21 UTCEG score recompute
  25. 2026-07-22 14:08 UTCEPSS rescore
Show 16 more
  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-16 13:46 UTCGHSA enrichment
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 13:09 UTCGHSA enrichment
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 12:32 UTCGHSA enrichment
  15. 2026-07-13 11:57 UTCEG score recompute
  16. 2026-07-13 11:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62147?
CVE-2026-62147 is a medium vulnerability published on July 13, 2026. 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.
When was CVE-2026-62147 disclosed?
CVE-2026-62147 was first published in the National Vulnerability Database on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62147 actively exploited?
CVE-2026-62147 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.8% of all scored CVEs.
What is the CVSS score of CVE-2026-62147?
CVE-2026-62147 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-62147?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62147, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62147

Explore →

Is Your Infrastructure Affected by CVE-2026-62147?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.