<?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://cve.radiocsirt.org</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>Mon, 16 Nov 2026 21:21:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-404805</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-404805</link>
      <description>EUVD-2026-404805</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-404805</guid>
    </item>
    <item>
      <title>fkie_cve-2026-97040</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-97040</link>
      <description>&lt;p&gt;Building a package containing a crafted &amp;#34;.syso&amp;#34; file could bypass cgo flag validation and inject arbitrary linker flags when linking. When loading &amp;#34;.syso&amp;#34; entries from a package archive, the linker only checked for recognized host object headers (ELF, Mach-O, PE, and XCOFF) before falling through to Go object parsing. A &amp;#34;.syso&amp;#34; file beginning with a &amp;#34;go object&amp;#34; header was parsed as a Go compiler object, allowing untrusted cgo metadata directives (such as &amp;#34;cgo_ldflag&amp;#34; or &amp;#34;cgo_dynamic_linker&amp;#34;) embedded in the &amp;#34;.syso&amp;#34; file to be passed to the external linker without validation. Additionally, &amp;#34;.syso&amp;#34; filenames longer than 16 bytes lost their &amp;#34;.syso&amp;#34; extension when truncated in archive headers, and unrecognized &amp;#34;.syso&amp;#34; formats forced external linking in pure-Go builds. The linker now rejects &amp;#34;.syso&amp;#34; files that are not recognized host object formats, and &amp;#34;cmd/go&amp;#34; and &amp;#34;cmd/pack&amp;#34; preserve the &amp;#34;.syso&amp;#34; suffix when truncating long archive member names.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Building a package containing a crafted &amp;#34;.syso&amp;#34; file could bypass cgo flag validation and inject arbitrary linker flags when linking. When loading &amp;#34;.syso&amp;#34; entries from a package archive, the linker only checked for recognized host object headers (ELF, Mach-O, PE, and XCOFF) before falling through to Go object parsing. A &amp;#34;.syso&amp;#34; file beginning with a &amp;#34;go object&amp;#34; header was parsed as a Go compiler object, allowing untrusted cgo metadata directives (such as &amp;#34;cgo_ldflag&amp;#34; or &amp;#34;cgo_dynamic_linker&amp;#34;) embedded in the &amp;#34;.syso&amp;#34; file to be passed to the external linker without validation. Additionally, &amp;#34;.syso&amp;#34; filenames longer than 16 bytes lost their &amp;#34;.syso&amp;#34; extension when truncated in archive headers, and unrecognized &amp;#34;.syso&amp;#34; formats forced external linking in pure-Go builds. The linker now rejects &amp;#34;.syso&amp;#34; files that are not recognized host object formats, and &amp;#34;cmd/go&amp;#34; and &amp;#34;cmd/pack&amp;#34; preserve the &amp;#34;.syso&amp;#34; suffix when truncating long archive member names.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-97040</guid>
    </item>
    <item>
      <title>GHSA-9767-p5x8-v2p2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9767-p5x8-v2p2</link>
      <description>&lt;p&gt;Building a package containing a crafted &amp;#34;.syso&amp;#34; file could bypass cgo flag validation and inject arbitrary linker flags when linking. When loading &amp;#34;.syso&amp;#34; entries from a package archive, the linker only checked for recognized host object headers (ELF, Mach-O, PE, and XCOFF) before falling through to Go object parsing. A &amp;#34;.syso&amp;#34; file beginning with a &amp;#34;go object&amp;#34; header was parsed as a Go compiler object, allowing untrusted cgo metadata directives (such as &amp;#34;cgo_ldflag&amp;#34; or &amp;#34;cgo_dynamic_linker&amp;#34;) embedded in the &amp;#34;.syso&amp;#34; file to be passed to the external linker without validation. Additionally, &amp;#34;.syso&amp;#34; filenames longer than 16 bytes lost their &amp;#34;.syso&amp;#34; extension when truncated in archive headers, and unrecognized &amp;#34;.syso&amp;#34; formats forced external linking in pure-Go builds. The linker now rejects &amp;#34;.syso&amp;#34; files that are not recognized host object formats, and &amp;#34;cmd/go&amp;#34; and &amp;#34;cmd/pack&amp;#34; preserve the &amp;#34;.syso&amp;#34; suffix when truncating long archive member names.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Building a package containing a crafted &amp;#34;.syso&amp;#34; file could bypass cgo flag validation and inject arbitrary linker flags when linking. When loading &amp;#34;.syso&amp;#34; entries from a package archive, the linker only checked for recognized host object headers (ELF, Mach-O, PE, and XCOFF) before falling through to Go object parsing. A &amp;#34;.syso&amp;#34; file beginning with a &amp;#34;go object&amp;#34; header was parsed as a Go compiler object, allowing untrusted cgo metadata directives (such as &amp;#34;cgo_ldflag&amp;#34; or &amp;#34;cgo_dynamic_linker&amp;#34;) embedded in the &amp;#34;.syso&amp;#34; file to be passed to the external linker without validation. Additionally, &amp;#34;.syso&amp;#34; filenames longer than 16 bytes lost their &amp;#34;.syso&amp;#34; extension when truncated in archive headers, and unrecognized &amp;#34;.syso&amp;#34; formats forced external linking in pure-Go builds. The linker now rejects &amp;#34;.syso&amp;#34; files that are not recognized host object formats, and &amp;#34;cmd/go&amp;#34; and &amp;#34;cmd/pack&amp;#34; preserve the &amp;#34;.syso&amp;#34; suffix when truncating long archive member names.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9767-p5x8-v2p2</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-97040 — Cgo directive injection via .syso files disguised as Go object files in cmd/go and cmd/link</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-97040</link>
      <description>msrc_CVE-2026-97040</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-97040</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-97040</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-97040</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 package containing a crafted &amp;#34;.syso&amp;#34; file could bypass cgo flag validation and inject arbitrary linker flags when linking. When loading &amp;#34;.syso&amp;#34; entries from a package archive, the linker only checked for recognized host object headers (ELF, Mach-O, PE, and XCOFF) before falling through to Go object parsing. A &amp;#34;.syso&amp;#34; file beginning with a &amp;#34;go object&amp;#34; header was parsed as a Go compiler object, allowing untrusted cgo metadata directives (such as &amp;#34;cgo_ldflag&amp;#34; or &amp;#34;cgo_dynamic_linker&amp;#34;) embedded in the &amp;#34;.syso&amp;#34; file to be passed to the external linker without validation. Additionally, &amp;#34;.syso&amp;#34; filenames longer than 16 bytes lost their &amp;#34;.syso&amp;#34; extension when truncated in archive headers, and unrecognized &amp;#34;.syso&amp;#34; formats forced external linking in pure-Go builds. The linker now rejects &amp;#34;.syso&amp;#34; files that are not recognized host object formats, and &amp;#34;cmd/go&amp;#34; and &amp;#34;cmd/pack&amp;#34; preserve the &amp;#34;.syso&amp;#34; suffix when truncating long archive member names.&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 package containing a crafted &amp;#34;.syso&amp;#34; file could bypass cgo flag validation and inject arbitrary linker flags when linking. When loading &amp;#34;.syso&amp;#34; entries from a package archive, the linker only checked for recognized host object headers (ELF, Mach-O, PE, and XCOFF) before falling through to Go object parsing. A &amp;#34;.syso&amp;#34; file beginning with a &amp;#34;go object&amp;#34; header was parsed as a Go compiler object, allowing untrusted cgo metadata directives (such as &amp;#34;cgo_ldflag&amp;#34; or &amp;#34;cgo_dynamic_linker&amp;#34;) embedded in the &amp;#34;.syso&amp;#34; file to be passed to the external linker without validation. Additionally, &amp;#34;.syso&amp;#34; filenames longer than 16 bytes lost their &amp;#34;.syso&amp;#34; extension when truncated in archive headers, and unrecognized &amp;#34;.syso&amp;#34; formats forced external linking in pure-Go builds. The linker now rejects &amp;#34;.syso&amp;#34; files that are not recognized host object formats, and &amp;#34;cmd/go&amp;#34; and &amp;#34;cmd/pack&amp;#34; preserve the &amp;#34;.syso&amp;#34; suffix when truncating long archive member names.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-97040</guid>
    </item>
  </channel>
</rss>
