<?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, 06 Oct 2026 21:46:47 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-361830</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361830</link>
      <description>EUVD-2026-361830</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361830</guid>
    </item>
    <item>
      <title>fkie_cve-2026-77846</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-77846</link>
      <description>&lt;p&gt;Improper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash_sqlite allows an attacker who controls a get_path/2 segment to traverse into nested JSON the application never exposed, disclosing private or sensitive? embedded fields.&lt;/p&gt;
&lt;p&gt;AshSqlite.SqlImplementation builds the SQLite json_extract path with &amp;#34;$.&amp;#34; &amp;lt;&amp;gt; Enum.join(right, &amp;#34;.&amp;#34;), so a single segment containing ., [, ], or $ re-interprets the JSON path (for example &amp;#34;private.secret&amp;#34; descends two levels instead of naming one key). The path is bound as a parameter, so this is confined to the JSON-path grammar rather than SQL. Any endpoint that lets user input reach a get_path segment (a common pick-a-field pattern) can read nested values it never meant to expose.&lt;/p&gt;
&lt;p&gt;This issue affects ash_sqlite: from 0.1.2-rc.0 before 0.2.18.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash_sqlite allows an attacker who controls a get_path/2 segment to traverse into nested JSON the application never exposed, disclosing private or sensitive? embedded fields.&lt;/p&gt;
&lt;p&gt;AshSqlite.SqlImplementation builds the SQLite json_extract path with &amp;#34;$.&amp;#34; &amp;lt;&amp;gt; Enum.join(right, &amp;#34;.&amp;#34;), so a single segment containing ., [, ], or $ re-interprets the JSON path (for example &amp;#34;private.secret&amp;#34; descends two levels instead of naming one key). The path is bound as a parameter, so this is confined to the JSON-path grammar rather than SQL. Any endpoint that lets user input reach a get_path segment (a common pick-a-field pattern) can read nested values it never meant to expose.&lt;/p&gt;
&lt;p&gt;This issue affects ash_sqlite: from 0.1.2-rc.0 before 0.2.18.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-77846</guid>
    </item>
  </channel>
</rss>
