Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 6.91% for the current model date.
BlackTreeCVE IntelligenceUnknown · Unknown
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Alpine findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | go | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.15.7-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
| Alpine v3.22v3.22 · community | go | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.15.7-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
| Alpine v3.21v3.21 · community | go | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.15.7-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Fix not verifiedGo before 1.14.14 and 1.15.x before 1.15.7 on Windows is vulnerable to Command Injection and remote code execution when using the "go get" command to fetch modules that make use of cgo (for example, cgo can execute a gcc program from an untrusted download).
Go before 1.14.14 and 1.15.x before 1.15.7 on Windows is vulnerable to Command Injection and remote code execution when using the "go get" command to fetch modules that make use of cgo (for example, cgo can execute a gcc program from an untrusted download).
The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
Go before 1.14.14 and 1.15.x before 1.15.7 on Windows is vulnerable to Command Injection and remote code execution when using the "go get" command to fetch modules that make use of cgo (for example, cgo can execute a gcc program from an untrusted download).
The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-427: Uncontrolled Search Path Element. The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
Published 26 Jan 2021 · Last source change 3 Aug 2024, 16:45 UTC · CWE-427 · Uncontrolled Search Path Element
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.