<?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:03:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97039 — Flag sanitization bypass via "#cgo pkg-config:" directives in cmd/go</title>
      <link>https://db.gcve.eu/vuln/cve-2026-97039</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 that uses &amp;#34;#cgo pkg-config:&amp;#34; directives could load untrusted pkg-config &amp;#34;.pc&amp;#34; files or inject unvalidated compiler and linker flags. The pkg-config flag allowlist previously permitted &amp;#34;--with-path=&amp;#34; and &amp;#34;--personality=&amp;#34;, allowed &amp;#34;--define-variable=&amp;#34; values beginning with &amp;#34;=&amp;#34; or &amp;#34;$&amp;#34; (which can rewrite paths in system &amp;#34;.pc&amp;#34; files into sysroot-prefixed &amp;#34;-L=&amp;#34; or &amp;#34;-L$SYSROOT&amp;#34; linker search paths), and allowed package arguments ending in &amp;#34;.pc&amp;#34; or containing path separators or &amp;#34;..&amp;#34;, which caused pkg-config to load local &amp;#34;.pc&amp;#34; files directly from the package directory. In addition, flags returned by &amp;#34;pkg-config --cflags&amp;#34; in cgoCPPFLAGS were not checked when determining whether internal linking is safe. The go command now disallows &amp;#34;--with-path=&amp;#34;, &amp;#34;--personality=&amp;#34;, leading &amp;#34;=&amp;#34; or &amp;#34;$&amp;#34; characters in &amp;#34;--define-variable=&amp;#34; values, and local &amp;#34;.pc&amp;#34; paths in &amp;#34;#cgo pkg-config:&amp;#34; directives, and inspects cgoCPPFLAGS when checking internal linking compatibility.&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 that uses &amp;#34;#cgo pkg-config:&amp;#34; directives could load untrusted pkg-config &amp;#34;.pc&amp;#34; files or inject unvalidated compiler and linker flags. The pkg-config flag allowlist previously permitted &amp;#34;--with-path=&amp;#34; and &amp;#34;--personality=&amp;#34;, allowed &amp;#34;--define-variable=&amp;#34; values beginning with &amp;#34;=&amp;#34; or &amp;#34;$&amp;#34; (which can rewrite paths in system &amp;#34;.pc&amp;#34; files into sysroot-prefixed &amp;#34;-L=&amp;#34; or &amp;#34;-L$SYSROOT&amp;#34; linker search paths), and allowed package arguments ending in &amp;#34;.pc&amp;#34; or containing path separators or &amp;#34;..&amp;#34;, which caused pkg-config to load local &amp;#34;.pc&amp;#34; files directly from the package directory. In addition, flags returned by &amp;#34;pkg-config --cflags&amp;#34; in cgoCPPFLAGS were not checked when determining whether internal linking is safe. The go command now disallows &amp;#34;--with-path=&amp;#34;, &amp;#34;--personality=&amp;#34;, leading &amp;#34;=&amp;#34; or &amp;#34;$&amp;#34; characters in &amp;#34;--define-variable=&amp;#34; values, and local &amp;#34;.pc&amp;#34; paths in &amp;#34;#cgo pkg-config:&amp;#34; directives, and inspects cgoCPPFLAGS when checking internal linking compatibility.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-97039</guid>
    </item>
  </channel>
</rss>
