Building a malicious package containing ".syso" files or cgo linker inputs could inject arbitrary linker flags or execute arbitrary code at link time. Linker input files—including ".syso" files, direct object or library inputs in "#cgo LDFLAGS", and libraries in "-L" directories—were passed to the external linker without validating their format or checking for embedded linker options. Across platforms, this allowed executing GNU ld implicit linker scripts disguised as libraries or ".syso" files (or loaded via "-l:" or "-l" containing path separators), injecting unallowlisted linker flags via PE/COFF ".drectve" sections on Windows or Mach-O "LC_LINKER_OPTION" load commands on Darwin, or invoking LTO plugins via GCC or LLVM LTO intermediate representation sections in ELF, PE/COFF, or Mach-O objects. The go command now verifies that ".syso" files, direct linker inputs, and libraries in "-L" directories are valid binary objects or archives that do not contain unallowlisted ".drectve" directives, "LC_LINKER_OPTION" load commands, or LTO IR sections, and disallows "-l:" and ":", "=", or path separators in "-l" flags.
CVE-2026-97038
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-11-11. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.
Also known asEUVD-2026-123107 (ENISA EUVD) · GHSA-q9p5-q4jx-v656 (GitHub Security Advisories) · GO-2026-6853 (OSV.dev)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHhigh confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.2% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.7%
- EPSS %ILE
- 53rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.7% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 11, 2026
Last Modified
November 17, 2026
Advisory Details (4)
Auto-updated Nov 16, 2026cmd/go: arbitrary code execution via crafted .syso files and cgo linker input files · Issue #82572 · golang/go · GitHub
https://go.dev/issue/82572Vendor Advisories for CVE-2026-97038(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-97038Microsoft Security Response Center (MSRC)HighMicrosoft CVSS 8.8
Microsoft security update for CVE-2026-97038
- RHSA-2026:99004Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:99003Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- GHSA-q9p5-q4jx-v656GitHub Security AdvisoriesHigh
Building a malicious package containing ".syso" files or cgo linker inputs could inject arbitrary...
Affected Packages
(4 across 3 ecosystems)
Debian:14(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-1.26 | 1.26.0-1 ... 1.26~rc3-2 (27 versions) |
| — |
| golang-1.27 | 1.27.0-1 ... 1.27~rc3-1 (13 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-1.19 | 1.19.10-1 ... 1.19.9-1 (12 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-1.24 | 1.24.12-1 ... 1.24.9-1 (10 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 25× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.5% · 46th percentile
- 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.5% · 46th percentile
- 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.5% · 46th percentile
- 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.5% · 46th percentile
- 2026-11-17 05:31 UTCVendor advisory
- 2026-11-17 05:31 UTCGHSA enrichmentGHSA-q9p5-q4jx-v656 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-17 05:00 UTCEchelonGraph re-scored
- 2026-11-17 05:00 UTCVendor advisory
- 2026-11-17 05:00 UTCGHSA enrichmentGHSA-q9p5-q4jx-v656 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-16 15:28 UTCVendor advisory
- 2026-11-16 15:28 UTCGHSA enrichmentGHSA-q9p5-q4jx-v656
- 2026-11-16 15:14 UTCEchelonGraph re-scoredFirst assessed: 8.8 HIGH
- 2026-11-16 15:14 UTCVendor advisory
- 2026-11-16 15:14 UTCGHSA enrichmentGHSA-q9p5-q4jx-v656
- 2026-11-16 15:13 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
- 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-12 22:32 UTCEchelonGraph re-scored
- 2026-11-12 22:32 UTCGHSA enrichmentGHSA-q9p5-q4jx-v656
- 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.3% · 16th percentile
- 2026-11-11 08:34 UTCGHSA enrichmentGHSA-q9p5-q4jx-v656
Show 4 moreShow fewer
- 2026-11-11 05:27 UTCNVD update
- 2026-11-11 04:00 UTCENISA EUVD ID recordedEUVD-2026-123107 · Source: ENISA EUVD
- 2026-11-11 03:20 UTCEchelonGraph re-scored
- 2026-11-11 03:19 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownDebian:14:golang-1.27
Frequently asked(5)
What is CVE-2026-97038?
When was the CVE record for CVE-2026-97038 published?
Is CVE-2026-97038 actively exploited?
What is the CVSS score of CVE-2026-97038?
How do I remediate CVE-2026-97038?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-97038
Is Your Infrastructure Affected by CVE-2026-97038?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.