<?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-08T00:46:10.370157+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/cleanstart-2026-gz01306</id>
    <title>CLEANSTART-2026-GZ01306 — Security fix for ghsa-cf98-j28v-49v6 applied in: grafana 13.1.0-r1</title>
    <updated>2026-10-08T00:46:10.394085+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: grafana</p>
<p>Security vulnerability affects the grafana package. This issue is resolved in later releases. See references for vulnerability details.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-gz01306"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-55170</id>
    <title>CVE-2026-55170 — OpenFGA MySQL backend: case-insensitive collation on identifier columns causes incorrect authorization decisions</title>
    <updated>2026-10-08T00:46:10.394140+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openfga</p>
<p>OpenFGA is an authorization/permission engine built for developers. Prior to 1.18.0, when MySQL is being used as the datastore and authorization decisions rely on case-sensitive user strings, the tuple, changelog, and authorization_model identifier columns can compare case-distinct values such as user:Alice and user:alice as equivalent, causing two distinct check requests to return the same response. This issue is fixed in 1.18.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-55170"/>
  </entry>
</feed>
