<?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://vulnerability.circl.lu</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>Fri, 02 Oct 2026 04:18:26 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-66353</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-66353</link>
      <description>&lt;p&gt;Improper Neutralization of Input During Web Page Generation (&amp;#39;Cross-site Scripting&amp;#39;) vulnerability in woylie doggo allows Reflected XSS.&lt;/p&gt;
&lt;p&gt;Doggo.normalize_value/2 in lib/doggo.ex returned date field values wrapped in {:safe, ...}, the Phoenix.HTML marker meaning &amp;#34;already escaped, emit verbatim&amp;#34;, without escaping them, so the value reached the value attribute of the &amp;lt;input&amp;gt; rendered by the field component unchanged. Any application rendering &amp;lt;.field type=&amp;#34;date&amp;#34;&amp;gt; over user-controlled params is affected through the ordinary Phoenix form round-trip, where a failed validation re-renders the submitted value. The pattern kept exactly the first ten bytes and discarded shorter values, capping a payload at ten bytes: enough to terminate the attribute and open an element or attach a short event handler, not enough to place attacker-chosen script inline. Only type=&amp;#34;date&amp;#34; is affected.&lt;/p&gt;
&lt;p&gt;This issue affects doggo: from 0.1.0 before 0.14.8.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Neutralization of Input During Web Page Generation (&amp;#39;Cross-site Scripting&amp;#39;) vulnerability in woylie doggo allows Reflected XSS.&lt;/p&gt;
&lt;p&gt;Doggo.normalize_value/2 in lib/doggo.ex returned date field values wrapped in {:safe, ...}, the Phoenix.HTML marker meaning &amp;#34;already escaped, emit verbatim&amp;#34;, without escaping them, so the value reached the value attribute of the &amp;lt;input&amp;gt; rendered by the field component unchanged. Any application rendering &amp;lt;.field type=&amp;#34;date&amp;#34;&amp;gt; over user-controlled params is affected through the ordinary Phoenix form round-trip, where a failed validation re-renders the submitted value. The pattern kept exactly the first ten bytes and discarded shorter values, capping a payload at ten bytes: enough to terminate the attribute and open an element or attach a short event handler, not enough to place attacker-chosen script inline. Only type=&amp;#34;date&amp;#34; is affected.&lt;/p&gt;
&lt;p&gt;This issue affects doggo: from 0.1.0 before 0.14.8.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-66353</guid>
    </item>
  </channel>
</rss>
