<?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:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97042 — Linker flag injection via cgo_import_dynamic and PE DLL names in cmd/cgo, cmd/compile, and cmd/link</title>
      <link>https://db.gcve.eu/vuln/cve-2026-97042</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go toolchain cmd/cgo, Go toolchain cmd/compile, Go toolchain cmd/link&lt;/p&gt;
&lt;p&gt;Building a malicious package that uses &amp;#34;//go:cgo_import_dynamic&amp;#34; or links against a crafted PE object on Windows could pass unsafe library arguments to the external linker. The compiler only checked the first character of the library name in &amp;#34;//go:cgo_import_dynamic&amp;#34; directives and skipped validation in cgo-generated files. In addition, on Windows, &amp;#34;cmd/cgo&amp;#34; and &amp;#34;cmd/link&amp;#34; did not validate imported DLL names extracted from PE object files before emitting &amp;#34;-l&amp;lt;name&amp;gt;&amp;#34; flags for the external linker, allowing a crafted DLL name containing &amp;#34;..&amp;#34; path traversal or special characters to reference arbitrary files on disk. The compiler now validates every character of the library name in &amp;#34;//go:cgo_import_dynamic&amp;#34; directives (including in cgo-generated files on Windows) and rejects &amp;#34;..&amp;#34; path traversal, and &amp;#34;cmd/cgo&amp;#34; and &amp;#34;cmd/link&amp;#34; reject PE imported DLL names containing path separators, &amp;#34;..&amp;#34;, &amp;#34;:&amp;#34;, or leading &amp;#34;-&amp;#34; or &amp;#34;@&amp;#34;.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go toolchain cmd/cgo, Go toolchain cmd/compile, Go toolchain cmd/link&lt;/p&gt;
&lt;p&gt;Building a malicious package that uses &amp;#34;//go:cgo_import_dynamic&amp;#34; or links against a crafted PE object on Windows could pass unsafe library arguments to the external linker. The compiler only checked the first character of the library name in &amp;#34;//go:cgo_import_dynamic&amp;#34; directives and skipped validation in cgo-generated files. In addition, on Windows, &amp;#34;cmd/cgo&amp;#34; and &amp;#34;cmd/link&amp;#34; did not validate imported DLL names extracted from PE object files before emitting &amp;#34;-l&amp;lt;name&amp;gt;&amp;#34; flags for the external linker, allowing a crafted DLL name containing &amp;#34;..&amp;#34; path traversal or special characters to reference arbitrary files on disk. The compiler now validates every character of the library name in &amp;#34;//go:cgo_import_dynamic&amp;#34; directives (including in cgo-generated files on Windows) and rejects &amp;#34;..&amp;#34; path traversal, and &amp;#34;cmd/cgo&amp;#34; and &amp;#34;cmd/link&amp;#34; reject PE imported DLL names containing path separators, &amp;#34;..&amp;#34;, &amp;#34;:&amp;#34;, or leading &amp;#34;-&amp;#34; or &amp;#34;@&amp;#34;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-97042</guid>
    </item>
  </channel>
</rss>
