<?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:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97034 — Arbitrary command execution via GCC spec files in cgo linker search directories in cmd/go</title>
      <link>https://db.gcve.eu/vuln/cve-2026-97034</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go toolchain cmd/go&lt;/p&gt;
&lt;p&gt;When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files (&amp;#34;specs&amp;#34; or &amp;#34;*.spec&amp;#34;). When linking with &amp;#34;-fopenmp&amp;#34;, &amp;#34;-fopenacc&amp;#34;, or &amp;#34;-fsanitize=&amp;#34; in &amp;#34;#cgo LDFLAGS&amp;#34;, GCC&amp;#39;s built-in link spec evaluates &amp;#34;%:include(libgomp.spec)&amp;#34; or &amp;#34;%:include(libsanitizer.spec)&amp;#34; and searches for spec files in &amp;#34;-L&amp;#34; and sysroot directories (including subdirectories and multilib sibling directories such as &amp;#34;../lib64&amp;#34;), as well as the working directory when &amp;#34;-fopenmp&amp;#34; or &amp;#34;-fopenacc&amp;#34; is used or when &amp;#34;-fsanitize=&amp;#34; is combined with &amp;#34;-static&amp;#34; or &amp;#34;-static-lib*&amp;#34;. The go command now rejects &amp;#34;-L&amp;#34;, &amp;#34;-isysroot&amp;#34;, and &amp;#34;-Wl,-syslibroot&amp;#34; directories (and the working and package directories when applicable) that contain GCC spec files, and disallows &amp;#34;@&amp;#34; and &amp;#34;-&amp;#34; prefixes in &amp;#34;-fsanitize=&amp;#34; compiler flag values.&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;When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files (&amp;#34;specs&amp;#34; or &amp;#34;*.spec&amp;#34;). When linking with &amp;#34;-fopenmp&amp;#34;, &amp;#34;-fopenacc&amp;#34;, or &amp;#34;-fsanitize=&amp;#34; in &amp;#34;#cgo LDFLAGS&amp;#34;, GCC&amp;#39;s built-in link spec evaluates &amp;#34;%:include(libgomp.spec)&amp;#34; or &amp;#34;%:include(libsanitizer.spec)&amp;#34; and searches for spec files in &amp;#34;-L&amp;#34; and sysroot directories (including subdirectories and multilib sibling directories such as &amp;#34;../lib64&amp;#34;), as well as the working directory when &amp;#34;-fopenmp&amp;#34; or &amp;#34;-fopenacc&amp;#34; is used or when &amp;#34;-fsanitize=&amp;#34; is combined with &amp;#34;-static&amp;#34; or &amp;#34;-static-lib*&amp;#34;. The go command now rejects &amp;#34;-L&amp;#34;, &amp;#34;-isysroot&amp;#34;, and &amp;#34;-Wl,-syslibroot&amp;#34; directories (and the working and package directories when applicable) that contain GCC spec files, and disallows &amp;#34;@&amp;#34; and &amp;#34;-&amp;#34; prefixes in &amp;#34;-fsanitize=&amp;#34; compiler flag values.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-97034</guid>
    </item>
  </channel>
</rss>
