<?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>Fri, 13 Nov 2026 05:05:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97038 — Arbitrary code execution via crafted .syso files and cgo linker input files in cmd/go</title>
      <link>https://db.gcve.eu/vuln/cve-2026-97038</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go toolchain cmd/go&lt;/p&gt;
&lt;p&gt;Building a malicious package containing &amp;#34;.syso&amp;#34; files or cgo linker inputs could inject arbitrary linker flags or execute arbitrary code at link time. Linker input files—including &amp;#34;.syso&amp;#34; files, direct object or library inputs in &amp;#34;#cgo LDFLAGS&amp;#34;, and libraries in &amp;#34;-L&amp;#34; directories—were passed to the external linker without validating their format or checking for embedded linker options. Across platforms, this allowed executing GNU ld implicit linker scripts disguised as libraries or &amp;#34;.syso&amp;#34; files (or loaded via &amp;#34;-l:&amp;lt;filename&amp;gt;&amp;#34; or &amp;#34;-l&amp;#34; containing path separators), injecting unallowlisted linker flags via PE/COFF &amp;#34;.drectve&amp;#34; sections on Windows or Mach-O &amp;#34;LC_LINKER_OPTION&amp;#34; load commands on Darwin, or invoking LTO plugins via GCC or LLVM LTO intermediate representation sections in ELF, PE/COFF, or Mach-O objects. The go command now verifies that &amp;#34;.syso&amp;#34; files, direct linker inputs, and libraries in &amp;#34;-L&amp;#34; directories are valid binary objects or archives that do not contain unallowlisted &amp;#34;.drectve&amp;#34; directives, &amp;#34;LC_LINKER_OPTION&amp;#34; load commands, or LTO IR sections, and disallows &amp;#34;-l:&amp;lt;filename&amp;gt;&amp;#34; and &amp;#34;:&amp;#34;, &amp;#34;=&amp;#34;, or path separators in &amp;#34;-l&amp;#34; flags.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go toolchain cmd/go&lt;/p&gt;
&lt;p&gt;Building a malicious package containing &amp;#34;.syso&amp;#34; files or cgo linker inputs could inject arbitrary linker flags or execute arbitrary code at link time. Linker input files—including &amp;#34;.syso&amp;#34; files, direct object or library inputs in &amp;#34;#cgo LDFLAGS&amp;#34;, and libraries in &amp;#34;-L&amp;#34; directories—were passed to the external linker without validating their format or checking for embedded linker options. Across platforms, this allowed executing GNU ld implicit linker scripts disguised as libraries or &amp;#34;.syso&amp;#34; files (or loaded via &amp;#34;-l:&amp;lt;filename&amp;gt;&amp;#34; or &amp;#34;-l&amp;#34; containing path separators), injecting unallowlisted linker flags via PE/COFF &amp;#34;.drectve&amp;#34; sections on Windows or Mach-O &amp;#34;LC_LINKER_OPTION&amp;#34; load commands on Darwin, or invoking LTO plugins via GCC or LLVM LTO intermediate representation sections in ELF, PE/COFF, or Mach-O objects. The go command now verifies that &amp;#34;.syso&amp;#34; files, direct linker inputs, and libraries in &amp;#34;-L&amp;#34; directories are valid binary objects or archives that do not contain unallowlisted &amp;#34;.drectve&amp;#34; directives, &amp;#34;LC_LINKER_OPTION&amp;#34; load commands, or LTO IR sections, and disallows &amp;#34;-l:&amp;lt;filename&amp;gt;&amp;#34; and &amp;#34;:&amp;#34;, &amp;#34;=&amp;#34;, or path separators in &amp;#34;-l&amp;#34; flags.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-97038</guid>
    </item>
  </channel>
</rss>
