https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 13 Nov 2026 04:46:52 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-97034 <p>When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files (&#34;specs&#34; or &#34;*.spec&#34;). When linking with &#34;-fopenmp&#34;, &#34;-fopenacc&#34;, or &#34;-fsanitize=&#34; in &#34;#cgo LDFLAGS&#34;, GCC&#39;s built-in link spec evaluates &#34;%:include(libgomp.spec)&#34; or &#34;%:include(libsanitizer.spec)&#34; and searches for spec files in &#34;-L&#34; and sysroot directories (including subdirectories and multilib sibling directories such as &#34;../lib64&#34;), as well as the working directory when &#34;-fopenmp&#34; or &#34;-fopenacc&#34; is used or when &#34;-fsanitize=&#34; is combined with &#34;-static&#34; or &#34;-static-lib*&#34;. The go command now rejects &#34;-L&#34;, &#34;-isysroot&#34;, and &#34;-Wl,-syslibroot&#34; directories (and the working and package directories when applicable) that contain GCC spec files, and disallows &#34;@&#34; and &#34;-&#34; prefixes in &#34;-fsanitize=&#34; compiler flag values.</p> <p>When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files (&#34;specs&#34; or &#34;*.spec&#34;). When linking with &#34;-fopenmp&#34;, &#34;-fopenacc&#34;, or &#34;-fsanitize=&#34; in &#34;#cgo LDFLAGS&#34;, GCC&#39;s built-in link spec evaluates &#34;%:include(libgomp.spec)&#34; or &#34;%:include(libsanitizer.spec)&#34; and searches for spec files in &#34;-L&#34; and sysroot directories (including subdirectories and multilib sibling directories such as &#34;../lib64&#34;), as well as the working directory when &#34;-fopenmp&#34; or &#34;-fopenacc&#34; is used or when &#34;-fsanitize=&#34; is combined with &#34;-static&#34; or &#34;-static-lib*&#34;. The go command now rejects &#34;-L&#34;, &#34;-isysroot&#34;, and &#34;-Wl,-syslibroot&#34; directories (and the working and package directories when applicable) that contain GCC spec files, and disallows &#34;@&#34; and &#34;-&#34; prefixes in &#34;-fsanitize=&#34; compiler flag values.</p> https://db.gcve.eu/vuln/fkie_cve-2026-97034 https://db.gcve.eu/vuln/ghsa-775q-r7gv-cr2x <p>When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files (&#34;specs&#34; or &#34;*.spec&#34;). When linking with &#34;-fopenmp&#34;, &#34;-fopenacc&#34;, or &#34;-fsanitize=&#34; in &#34;#cgo LDFLAGS&#34;, GCC&#39;s built-in link spec evaluates &#34;%:include(libgomp.spec)&#34; or &#34;%:include(libsanitizer.spec)&#34; and searches for spec files in &#34;-L&#34; and sysroot directories (including subdirectories and multilib sibling directories such as &#34;../lib64&#34;), as well as the working directory when &#34;-fopenmp&#34; or &#34;-fopenacc&#34; is used or when &#34;-fsanitize=&#34; is combined with &#34;-static&#34; or &#34;-static-lib*&#34;. The go command now rejects &#34;-L&#34;, &#34;-isysroot&#34;, and &#34;-Wl,-syslibroot&#34; directories (and the working and package directories when applicable) that contain GCC spec files, and disallows &#34;@&#34; and &#34;-&#34; prefixes in &#34;-fsanitize=&#34; compiler flag values.</p> <p>When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files (&#34;specs&#34; or &#34;*.spec&#34;). When linking with &#34;-fopenmp&#34;, &#34;-fopenacc&#34;, or &#34;-fsanitize=&#34; in &#34;#cgo LDFLAGS&#34;, GCC&#39;s built-in link spec evaluates &#34;%:include(libgomp.spec)&#34; or &#34;%:include(libsanitizer.spec)&#34; and searches for spec files in &#34;-L&#34; and sysroot directories (including subdirectories and multilib sibling directories such as &#34;../lib64&#34;), as well as the working directory when &#34;-fopenmp&#34; or &#34;-fopenacc&#34; is used or when &#34;-fsanitize=&#34; is combined with &#34;-static&#34; or &#34;-static-lib*&#34;. The go command now rejects &#34;-L&#34;, &#34;-isysroot&#34;, and &#34;-Wl,-syslibroot&#34; directories (and the working and package directories when applicable) that contain GCC spec files, and disallows &#34;@&#34; and &#34;-&#34; prefixes in &#34;-fsanitize=&#34; compiler flag values.</p> https://db.gcve.eu/vuln/ghsa-775q-r7gv-cr2x https://db.gcve.eu/vuln/opensuse-su-2026:12529-1 <p>go1.26-1.26.11-1.1 on GA media</p> <p>go1.26-1.26.11-1.1 on GA media</p> https://db.gcve.eu/vuln/opensuse-su-2026:12529-1 https://db.gcve.eu/vuln/ubuntu-cve-2026-97034 <p><strong>Affected:</strong> 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</p> <p>When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files (&#34;specs&#34; or &#34;*.spec&#34;). When linking with &#34;-fopenmp&#34;, &#34;-fopenacc&#34;, or &#34;-fsanitize=&#34; in &#34;#cgo LDFLAGS&#34;, GCC&#39;s built-in link spec evaluates &#34;%:include(libgomp.spec)&#34; or &#34;%:include(libsanitizer.spec)&#34; and searches for spec files in &#34;-L&#34; and sysroot directories (including subdirectories and multilib sibling directories such as &#34;../lib64&#34;), as well as the working directory when &#34;-fopenmp&#34; or &#34;-fopenacc&#34; is used or when &#34;-fsanitize=&#34; is combined with &#34;-static&#34; or &#34;-static-lib*&#34;. The go command now rejects &#34;-L&#34;, &#34;-isysroot&#34;, and &#34;-Wl,-syslibroot&#34; directories (and the working and package directories when applicable) that contain GCC spec files, and disallows &#34;@&#34; and &#34;-&#34; prefixes in &#34;-fsanitize=&#34; compiler flag values.</p> <p><strong>Affected:</strong> 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</p> <p>When using GCC, building a malicious package that uses cgo could cause arbitrary command execution at link time via untrusted GCC spec files (&#34;specs&#34; or &#34;*.spec&#34;). When linking with &#34;-fopenmp&#34;, &#34;-fopenacc&#34;, or &#34;-fsanitize=&#34; in &#34;#cgo LDFLAGS&#34;, GCC&#39;s built-in link spec evaluates &#34;%:include(libgomp.spec)&#34; or &#34;%:include(libsanitizer.spec)&#34; and searches for spec files in &#34;-L&#34; and sysroot directories (including subdirectories and multilib sibling directories such as &#34;../lib64&#34;), as well as the working directory when &#34;-fopenmp&#34; or &#34;-fopenacc&#34; is used or when &#34;-fsanitize=&#34; is combined with &#34;-static&#34; or &#34;-static-lib*&#34;. The go command now rejects &#34;-L&#34;, &#34;-isysroot&#34;, and &#34;-Wl,-syslibroot&#34; directories (and the working and package directories when applicable) that contain GCC spec files, and disallows &#34;@&#34; and &#34;-&#34; prefixes in &#34;-fsanitize=&#34; compiler flag values.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-97034 https://db.gcve.eu/vuln/wid-sec-w-2026-4370 <p>Ein Angreifer kann mehrere Schwachstellen in Golang Go ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Golang Go ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://db.gcve.eu/vuln/wid-sec-w-2026-4370