CVE-2025-2842

MEDIUMNVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
20(Track)
EG Risk 20/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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

April 2, 2025

Last Modified

September 8, 2026

Advisory Details (5)

Auto-updated Jul 20, 2026
Patch available. Sources: redhat, github_pr.
github_pr Patch Available

Fix CVE-2025-2842: Limit granted permissions of the Tempo Service Account when enabling the Jaeger UI Monitor tab on OpenShift

Patch available: grafana/tempo-operator v0.16.0 (PR #1144 merged 2025-04-11)

https://github.com/grafana/tempo-operator/pull/1144
redhat

2355219 – (CVE-2025-2842) CVE-2025-2842 tempo-operator: Tempo Operator Token Exposition lead to read sensitive data

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

cve-details

https://access.redhat.com/security/cve/CVE-2025-2842
redhat Patch Available
https://access.redhat.com/errata/RHSA-2025:3740
redhat Patch Available
https://access.redhat.com/errata/RHSA-2025:3607

Vendor Advisories for CVE-2025-2842(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhosdt/tempo-rhel8-operator:rhosdt-3.5-17440289712025-04-09redhat
redhatrhosdt/tempo-rhel8-operator:rhosdt-3.5-17431622652025-04-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/grafana/tempo-operator—0.16.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 48× 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.

Showing the most recent 100 of 233 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-16 05:13 UTCEPSS rescore
  4. 2026-09-13 16:46 UTCEPSS rescore
  5. 2026-09-12 15:00 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-11 09:35 UTCEPSS rescore
  8. 2026-09-10 09:33 UTCEPSS rescore
  9. 2026-09-08 23:03 UTCEG score recompute
  10. 2026-09-08 23:03 UTCVendor advisory
  11. 2026-09-08 21:59 UTCEPSS rescore
  12. 2026-09-08 16:15 UTCVendor advisory
  13. 2026-09-07 22:33 UTCVendor advisory
  14. 2026-09-07 21:44 UTCEG score recompute
  15. 2026-09-07 21:44 UTCVendor advisory
  16. 2026-09-07 16:00 UTCEPSS rescore
  17. 2026-09-06 22:32 UTCVendor advisory
  18. 2026-09-06 21:55 UTCVendor advisory
  19. 2026-09-06 21:30 UTCVendor advisory
  20. 2026-09-06 20:24 UTCEG score recompute
  21. 2026-09-06 20:24 UTCVendor advisory
  22. 2026-09-06 13:46 UTCEPSS rescore
  23. 2026-09-06 13:46 UTCEPSS rescore
  24. 2026-09-05 18:23 UTCVendor advisory
  25. 2026-09-05 17:42 UTCVendor advisory
Show 75 more
  1. 2026-09-05 16:17 UTCEG score recompute
  2. 2026-09-05 16:17 UTCVendor advisory
  3. 2026-09-04 05:05 UTCEPSS rescore
  4. 2026-09-02 14:11 UTCEPSS rescore
  5. 2026-09-01 13:53 UTCEPSS rescore
  6. 2026-08-30 19:16 UTCEPSS rescore
  7. 2026-08-30 19:16 UTCEPSS rescore
  8. 2026-08-30 01:21 UTCEPSS rescore
  9. 2026-08-28 21:40 UTCEPSS rescore
  10. 2026-08-27 14:24 UTCEPSS rescore
  11. 2026-08-26 14:45 UTCEPSS rescore
  12. 2026-08-25 13:48 UTCEPSS rescore
  13. 2026-08-25 10:23 UTCVendor advisory
  14. 2026-08-25 09:36 UTCVendor advisory
  15. 2026-08-25 08:24 UTCVendor advisory
  16. 2026-08-25 08:06 UTCEG score recompute
  17. 2026-08-25 08:06 UTCVendor advisory
  18. 2026-08-24 14:16 UTCEPSS rescore
  19. 2026-08-23 14:20 UTCVendor advisory
  20. 2026-08-23 13:51 UTCEG score recompute
  21. 2026-08-23 13:51 UTCVendor advisory
  22. 2026-08-23 00:18 UTCEPSS rescore
  23. 2026-08-21 23:48 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-19 03:20 UTCVendor advisory
  26. 2026-08-19 03:14 UTCVendor advisory
  27. 2026-08-19 01:20 UTCVendor advisory
  28. 2026-08-19 01:13 UTCEG score recompute
  29. 2026-08-19 01:13 UTCVendor advisory
  30. 2026-08-18 13:47 UTCEPSS rescore
  31. 2026-08-17 13:46 UTCEPSS rescore
  32. 2026-08-17 13:23 UTCVendor advisory
  33. 2026-08-17 12:38 UTCVendor advisory
  34. 2026-08-17 10:25 UTCVendor advisory
  35. 2026-08-17 09:38 UTCEG score recompute
  36. 2026-08-17 09:38 UTCVendor advisory
  37. 2026-08-16 14:55 UTCEPSS rescore
  38. 2026-08-16 13:33 UTCVendor advisory
  39. 2026-08-16 12:37 UTCEG score recompute
  40. 2026-08-16 12:37 UTCVendor advisory
  41. 2026-08-16 02:13 UTCEPSS rescore
  42. 2026-08-15 01:29 UTCEPSS rescore
  43. 2026-08-13 21:59 UTCEPSS rescore
  44. 2026-08-12 13:50 UTCEPSS rescore
  45. 2026-08-10 23:59 UTCEPSS rescore
  46. 2026-08-09 18:20 UTCVendor advisory
  47. 2026-08-09 18:11 UTCVendor advisory
  48. 2026-08-09 17:16 UTCEG score recompute
  49. 2026-08-09 17:16 UTCVendor advisory
  50. 2026-08-09 13:45 UTCEPSS rescore
  51. 2026-08-09 06:24 UTCVendor advisory
  52. 2026-08-09 05:50 UTCVendor advisory
  53. 2026-08-09 05:23 UTCVendor advisory
  54. 2026-08-09 04:40 UTCEG score recompute
  55. 2026-08-09 04:40 UTCVendor advisory
  56. 2026-08-07 16:26 UTCEPSS rescore
  57. 2026-08-06 13:46 UTCEPSS rescore
  58. 2026-08-05 19:16 UTCEPSS rescore
  59. 2026-08-04 15:09 UTCEPSS rescore
  60. 2026-08-04 10:37 UTCEPSS rescore
  61. 2026-08-04 05:28 UTCVendor advisory
  62. 2026-08-04 04:39 UTCVendor advisory
  63. 2026-08-03 23:30 UTCVendor advisory
  64. 2026-08-03 22:28 UTCVendor advisory
  65. 2026-08-03 12:35 UTCVendor advisory
  66. 2026-08-03 11:28 UTCEG score recompute
  67. 2026-08-03 11:28 UTCVendor advisory
  68. 2026-08-03 10:35 UTCEPSS rescore
  69. 2026-08-03 08:26 UTCVendor advisory
  70. 2026-08-03 07:54 UTCVendor advisory
  71. 2026-08-02 13:30 UTCVendor advisory
  72. 2026-08-02 12:39 UTCEG score recompute
  73. 2026-08-02 12:39 UTCVendor advisory
  74. 2026-08-02 02:26 UTCEPSS rescore
  75. 2026-08-01 04:15 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-2842?
CVE-2025-2842 is a medium vulnerability published on April 2, 2025. 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…
When was CVE-2025-2842 disclosed?
CVE-2025-2842 was first published in the National Vulnerability Database on April 2, 2025, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-2842 actively exploited?
CVE-2025-2842 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 67.8% of all scored CVEs.
What is the CVSS score of CVE-2025-2842?
CVE-2025-2842 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2025-2842?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-2842, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-2842

Explore →

Is Your Infrastructure Affected by CVE-2025-2842?

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

Start Free Scan →Browse All CVEs