<?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://db.gcve.eu</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, 18 Nov 2026 08:56:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-121757 — CP949 decoder may read past input</title>
      <link>https://db.gcve.eu/vuln/cve-2026-121757</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; The GNU C Library glibc&lt;/p&gt;
&lt;p&gt;Converting crafted CP949 input to UTF-8 character encoding and ignoring invalid characters, in the GNU C Library version 2.1 or later may result in the converter reading past the end of the input buffer, causing the calling application to crash.&lt;/p&gt;
&lt;p&gt;When the CP949 decoder encounters an invalid input byte sequence like &amp;#39;\xa2\xe8&amp;#39; it ends up advancing the pointer tracking the read buffer position twice.  If //IGNORE is set on the destination encoding and this sequence is at the end of the input buffer, the decoder may then end up reading past the bounds of the input buffer.  To exploit this, the target iconv function needs to set //IGNORE on the destination of the conversion and the input and encoding needs to be attacker controlled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; The GNU C Library glibc&lt;/p&gt;
&lt;p&gt;Converting crafted CP949 input to UTF-8 character encoding and ignoring invalid characters, in the GNU C Library version 2.1 or later may result in the converter reading past the end of the input buffer, causing the calling application to crash.&lt;/p&gt;
&lt;p&gt;When the CP949 decoder encounters an invalid input byte sequence like &amp;#39;\xa2\xe8&amp;#39; it ends up advancing the pointer tracking the read buffer position twice.  If //IGNORE is set on the destination encoding and this sequence is at the end of the input buffer, the decoder may then end up reading past the bounds of the input buffer.  To exploit this, the target iconv function needs to set //IGNORE on the destination of the conversion and the input and encoding needs to be attacker controlled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-121757</guid>
    </item>
  </channel>
</rss>
