<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T10:41:05.830986+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-379295</id>
    <title>EUVD-2026-379295</title>
    <updated>2026-10-03T10:41:05.894846+00:00</updated>
    <content>EUVD-2026-379295</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-379295"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-13720</id>
    <title>fkie_cve-2026-13720</title>
    <updated>2026-10-03T10:41:05.894897+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An Editor can set file-provisioning metadata (the grafana.app/managedBy, grafana.app/managerId and grafana.app/sourcePath annotations) when creating a dashboard through the dashboard API, because these fields were stored without an authorization check. The dashboard then appears file-provisioned, and administrators can no longer update or delete it through Grafana. The impact is limited to the same organization and no data is exposed.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-13720"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9q62-r26p-xcjv</id>
    <title>GHSA-9q62-r26p-xcjv</title>
    <updated>2026-10-03T10:41:05.894947+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An Editor can set file-provisioning metadata (the grafana.app/managedBy, grafana.app/managerId and grafana.app/sourcePath annotations) when creating a dashboard through the dashboard API, because these fields were stored without an authorization check. The dashboard then appears file-provisioned, and administrators can no longer update or delete it through Grafana. The impact is limited to the same organization and no data is exposed.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9q62-r26p-xcjv"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:74164</id>
    <title>RHSA-2026:74164 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
    <updated>2026-10-03T10:41:05.894978+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>github.com/grafana/grafana: Grafana: Information disclosure via alert rules list API grafana: grafana: Dashboard modification lockout via forged file-provisioning metadata grafana: Stored cross-site scripting in the Geomap panel allows privilege escalation grafana: grafana: Authorization bypass via missing destination folder permission check</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:74164"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3675</id>
    <title>WID-SEC-W-2026-3675 — Grafana: Mehrere Schwachstellen</title>
    <updated>2026-10-03T10:41:05.895018+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Grafana ausnutzen, um Informationen offenzulegen und Daten zu manipulieren.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3675"/>
  </entry>
</feed>
