<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 13 Oct 2026 04:24:52 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-365372</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-365372</link>
      <description>EUVD-2026-365372</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-365372</guid>
    </item>
    <item>
      <title>fkie_cve-2025-2842</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-2842</link>
      <description>&lt;p&gt;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 &amp;#39;create&amp;#39; permissions on TempoStack and &amp;#39;get&amp;#39; 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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 &amp;#39;create&amp;#39; permissions on TempoStack and &amp;#39;get&amp;#39; 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-2842</guid>
    </item>
    <item>
      <title>GHSA-5xf3-gmx4-529v — Grafana Tempo Operator Vulnerable to Exposure of Sensitive Information to an Unauthorized Actor</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5xf3-gmx4-529v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/grafana/tempo-operator&lt;/p&gt;
&lt;p&gt;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 &amp;#39;create&amp;#39; permissions on TempoStack and &amp;#39;get&amp;#39; 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/grafana/tempo-operator&lt;/p&gt;
&lt;p&gt;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 &amp;#39;create&amp;#39; permissions on TempoStack and &amp;#39;get&amp;#39; 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5xf3-gmx4-529v</guid>
    </item>
    <item>
      <title>RHSA-2025:3607 — Red Hat Security Advisory: Red Hat OpenShift distributed tracing platform (Tempo) 3.5.1 release</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:3607</link>
      <description>&lt;p&gt;tempo-operator: ServiceAccount Token Exposure Leading to Token and Subject Access Reviews in OpenShift Tempo Operator tempo-operator: Tempo Operator Token Exposition lead to read sensitive data golang-jwt/jwt: jwt-go allows excessive memory allocation during header parsing&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;tempo-operator: ServiceAccount Token Exposure Leading to Token and Subject Access Reviews in OpenShift Tempo Operator tempo-operator: Tempo Operator Token Exposition lead to read sensitive data golang-jwt/jwt: jwt-go allows excessive memory allocation during header parsing&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:3607</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0711 — Red Hat OpenShift (Tempo): Mehrere Schwachstellen ermöglichen Offenlegung von Informationen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0711</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0711</guid>
    </item>
  </channel>
</rss>
