<?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>Wed, 07 Oct 2026 21:09:14 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-361834</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361834</link>
      <description>EUVD-2026-361834</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361834</guid>
    </item>
    <item>
      <title>fkie_cve-2026-78691</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-78691</link>
      <description>&lt;p&gt;Improper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash_sql allows a user who supplies a search term to contains/2, string_starts_with/2, or string_ends_with/2 to inject live SQL LIKE wildcards, turning a literal substring search into an attacker-controlled pattern match.&lt;/p&gt;
&lt;p&gt;The escape helpers in AshSql.Expr prefix % and _ with a backslash but never escape a backslash already present in the input. Because backslash is the default LIKE escape character, the escaping defeats itself: the input \% becomes the pattern fragment \\%, where \\ is a literal backslash and the attacker&amp;#39;s % remains a live wildcard. The search value stays parameterized, so this is confined to the LIKE pattern grammar rather than full SQL. An attacker can widen matches to probe values, slip past a negated contains(...) guard, or crash the query with a trailing lone backslash.&lt;/p&gt;
&lt;p&gt;This issue affects ash_sql: from 0.1.1-rc.10 before 0.7.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash_sql allows a user who supplies a search term to contains/2, string_starts_with/2, or string_ends_with/2 to inject live SQL LIKE wildcards, turning a literal substring search into an attacker-controlled pattern match.&lt;/p&gt;
&lt;p&gt;The escape helpers in AshSql.Expr prefix % and _ with a backslash but never escape a backslash already present in the input. Because backslash is the default LIKE escape character, the escaping defeats itself: the input \% becomes the pattern fragment \\%, where \\ is a literal backslash and the attacker&amp;#39;s % remains a live wildcard. The search value stays parameterized, so this is confined to the LIKE pattern grammar rather than full SQL. An attacker can widen matches to probe values, slip past a negated contains(...) guard, or crash the query with a trailing lone backslash.&lt;/p&gt;
&lt;p&gt;This issue affects ash_sql: from 0.1.1-rc.10 before 0.7.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-78691</guid>
    </item>
  </channel>
</rss>
