<?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 04:46:51 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-97037</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-97037</link>
      <description>&lt;p&gt;Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script files to the host linker via &amp;#34;#cgo LDFLAGS&amp;#34;. Split &amp;#34;-Wl,&amp;#34; flags that consume a following argument (such as &amp;#34;-Wl,-rpath&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, and &amp;#34;-Wl,-undefined&amp;#34;) previously accepted a bare second argument without a &amp;#34;-Wl,&amp;#34; prefix, which the compiler driver passes directly to the linker as a positional input file. Additionally, when using GNU ld.bfd, flags such as &amp;#34;-framework&amp;#34;, &amp;#34;-Wl,-framework&amp;#34;, &amp;#34;-Wl,-undefined&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, &amp;#34;-Wl,-R&amp;#34;, &amp;#34;-Wl,-subsystem&amp;#34;, and (on non-Darwin platforms) &amp;#34;-Wl,-sectcreate&amp;#34; could cause ld.bfd to interpret their arguments as linker scripts if they named a regular file on disk. The go command now requires a &amp;#34;-Wl,&amp;#34; prefix on the second token of split &amp;#34;-Wl,&amp;#34; flags (except &amp;#34;-Wl,-R&amp;#34;), verifies that these flags do not reference linker script files, and disallows bare &amp;#34;-Wl,--warn-backrefs-exclude&amp;#34;.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script files to the host linker via &amp;#34;#cgo LDFLAGS&amp;#34;. Split &amp;#34;-Wl,&amp;#34; flags that consume a following argument (such as &amp;#34;-Wl,-rpath&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, and &amp;#34;-Wl,-undefined&amp;#34;) previously accepted a bare second argument without a &amp;#34;-Wl,&amp;#34; prefix, which the compiler driver passes directly to the linker as a positional input file. Additionally, when using GNU ld.bfd, flags such as &amp;#34;-framework&amp;#34;, &amp;#34;-Wl,-framework&amp;#34;, &amp;#34;-Wl,-undefined&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, &amp;#34;-Wl,-R&amp;#34;, &amp;#34;-Wl,-subsystem&amp;#34;, and (on non-Darwin platforms) &amp;#34;-Wl,-sectcreate&amp;#34; could cause ld.bfd to interpret their arguments as linker scripts if they named a regular file on disk. The go command now requires a &amp;#34;-Wl,&amp;#34; prefix on the second token of split &amp;#34;-Wl,&amp;#34; flags (except &amp;#34;-Wl,-R&amp;#34;), verifies that these flags do not reference linker script files, and disallows bare &amp;#34;-Wl,--warn-backrefs-exclude&amp;#34;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-97037</guid>
    </item>
    <item>
      <title>GHSA-f47v-97w8-qc5g</title>
      <link>https://db.gcve.eu/vuln/ghsa-f47v-97w8-qc5g</link>
      <description>&lt;p&gt;Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script files to the host linker via &amp;#34;#cgo LDFLAGS&amp;#34;. Split &amp;#34;-Wl,&amp;#34; flags that consume a following argument (such as &amp;#34;-Wl,-rpath&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, and &amp;#34;-Wl,-undefined&amp;#34;) previously accepted a bare second argument without a &amp;#34;-Wl,&amp;#34; prefix, which the compiler driver passes directly to the linker as a positional input file. Additionally, when using GNU ld.bfd, flags such as &amp;#34;-framework&amp;#34;, &amp;#34;-Wl,-framework&amp;#34;, &amp;#34;-Wl,-undefined&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, &amp;#34;-Wl,-R&amp;#34;, &amp;#34;-Wl,-subsystem&amp;#34;, and (on non-Darwin platforms) &amp;#34;-Wl,-sectcreate&amp;#34; could cause ld.bfd to interpret their arguments as linker scripts if they named a regular file on disk. The go command now requires a &amp;#34;-Wl,&amp;#34; prefix on the second token of split &amp;#34;-Wl,&amp;#34; flags (except &amp;#34;-Wl,-R&amp;#34;), verifies that these flags do not reference linker script files, and disallows bare &amp;#34;-Wl,--warn-backrefs-exclude&amp;#34;.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script files to the host linker via &amp;#34;#cgo LDFLAGS&amp;#34;. Split &amp;#34;-Wl,&amp;#34; flags that consume a following argument (such as &amp;#34;-Wl,-rpath&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, and &amp;#34;-Wl,-undefined&amp;#34;) previously accepted a bare second argument without a &amp;#34;-Wl,&amp;#34; prefix, which the compiler driver passes directly to the linker as a positional input file. Additionally, when using GNU ld.bfd, flags such as &amp;#34;-framework&amp;#34;, &amp;#34;-Wl,-framework&amp;#34;, &amp;#34;-Wl,-undefined&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, &amp;#34;-Wl,-R&amp;#34;, &amp;#34;-Wl,-subsystem&amp;#34;, and (on non-Darwin platforms) &amp;#34;-Wl,-sectcreate&amp;#34; could cause ld.bfd to interpret their arguments as linker scripts if they named a regular file on disk. The go command now requires a &amp;#34;-Wl,&amp;#34; prefix on the second token of split &amp;#34;-Wl,&amp;#34; flags (except &amp;#34;-Wl,-R&amp;#34;), verifies that these flags do not reference linker script files, and disallows bare &amp;#34;-Wl,--warn-backrefs-exclude&amp;#34;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-f47v-97w8-qc5g</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:12529-1 — go1.26-1.26.11-1.1 on GA media</title>
      <link>https://db.gcve.eu/vuln/opensuse-su-2026:12529-1</link>
      <description>&lt;p&gt;go1.26-1.26.11-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;go1.26-1.26.11-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/opensuse-su-2026:12529-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-97037</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-97037</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: golang-1.10, Ubuntu:16.04:LTS: golang-1.10, Ubuntu:16.04:LTS: golang-1.6, Ubuntu:Pro:16.04:LTS: golang-1.13, Ubuntu:Pro:16.04:LTS: golang-1.18, Ubuntu:18.04:LTS: golang-1.10, Ubuntu:Pro:18.04:LTS: golang-1.13, Ubuntu:Pro:18.04:LTS: golang-1.16, Ubuntu:Pro:18.04:LTS: golang-1.18, Ubuntu:18.04:LTS: golang-1.8 and 30 more&lt;/p&gt;
&lt;p&gt;Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script files to the host linker via &amp;#34;#cgo LDFLAGS&amp;#34;. Split &amp;#34;-Wl,&amp;#34; flags that consume a following argument (such as &amp;#34;-Wl,-rpath&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, and &amp;#34;-Wl,-undefined&amp;#34;) previously accepted a bare second argument without a &amp;#34;-Wl,&amp;#34; prefix, which the compiler driver passes directly to the linker as a positional input file. Additionally, when using GNU ld.bfd, flags such as &amp;#34;-framework&amp;#34;, &amp;#34;-Wl,-framework&amp;#34;, &amp;#34;-Wl,-undefined&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, &amp;#34;-Wl,-R&amp;#34;, &amp;#34;-Wl,-subsystem&amp;#34;, and (on non-Darwin platforms) &amp;#34;-Wl,-sectcreate&amp;#34; could cause ld.bfd to interpret their arguments as linker scripts if they named a regular file on disk. The go command now requires a &amp;#34;-Wl,&amp;#34; prefix on the second token of split &amp;#34;-Wl,&amp;#34; flags (except &amp;#34;-Wl,-R&amp;#34;), verifies that these flags do not reference linker script files, and disallows bare &amp;#34;-Wl,--warn-backrefs-exclude&amp;#34;.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: golang-1.10, Ubuntu:16.04:LTS: golang-1.10, Ubuntu:16.04:LTS: golang-1.6, Ubuntu:Pro:16.04:LTS: golang-1.13, Ubuntu:Pro:16.04:LTS: golang-1.18, Ubuntu:18.04:LTS: golang-1.10, Ubuntu:Pro:18.04:LTS: golang-1.13, Ubuntu:Pro:18.04:LTS: golang-1.16, Ubuntu:Pro:18.04:LTS: golang-1.18, Ubuntu:18.04:LTS: golang-1.8 and 30 more&lt;/p&gt;
&lt;p&gt;Building a malicious package that uses cgo could cause arbitrary code execution at link time by passing linker script files to the host linker via &amp;#34;#cgo LDFLAGS&amp;#34;. Split &amp;#34;-Wl,&amp;#34; flags that consume a following argument (such as &amp;#34;-Wl,-rpath&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, and &amp;#34;-Wl,-undefined&amp;#34;) previously accepted a bare second argument without a &amp;#34;-Wl,&amp;#34; prefix, which the compiler driver passes directly to the linker as a positional input file. Additionally, when using GNU ld.bfd, flags such as &amp;#34;-framework&amp;#34;, &amp;#34;-Wl,-framework&amp;#34;, &amp;#34;-Wl,-undefined&amp;#34;, &amp;#34;-Wl,--just-symbols&amp;#34;, &amp;#34;-Wl,-R&amp;#34;, &amp;#34;-Wl,-subsystem&amp;#34;, and (on non-Darwin platforms) &amp;#34;-Wl,-sectcreate&amp;#34; could cause ld.bfd to interpret their arguments as linker scripts if they named a regular file on disk. The go command now requires a &amp;#34;-Wl,&amp;#34; prefix on the second token of split &amp;#34;-Wl,&amp;#34; flags (except &amp;#34;-Wl,-R&amp;#34;), verifies that these flags do not reference linker script files, and disallows bare &amp;#34;-Wl,--warn-backrefs-exclude&amp;#34;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-97037</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4370 — Golang Go: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4370</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Golang Go ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Golang Go ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4370</guid>
    </item>
  </channel>
</rss>
