# CVE-2020-26284: Hugo can execute a binary from the current directory on Windows

> Attackers can execute arbitrary binaries on Windows by placing malicious files in the current directory when running Hugo.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-26284, GHSA-8j34-9876-pvfq

## What is CVE-2020-26284?

CVE-2020-26284 is a high-severity command injection vulnerability in gohugoio hugo, published on 21 Dec 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Hugo is a fast and Flexible Static Site Generator built in Go. Hugo depends on Go's `os/exec` for certain features, e.g. for rendering of Pandoc documents if these binaries are found in the system `%PATH%` on Windows. In Hugo before version 0.79.1, if a malicious file with the same name (`exe` or `bat`) is found in the current working directory at the time of running `hugo`, the malicious command will be invoked instead of the system one. Windows users who run `hugo` inside untrusted Hugo sites are affected. Users should upgrade to Hugo v0.79.1. Other than avoiding untrusted Hugo sites, there is no workaround.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2020-26284?

2 open source packages ship an affected version, including github.com/gohugoio/hugo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gohugoio/hugo` | Go | All versions | 0.79.1 |
| `github.com/gohugoio/hugo` | Go | All versions | 0.79.1 |

Products: Gohugo Hugo.

## How do I fix CVE-2020-26284?

Upgrade github.com/gohugoio/hugo to 0.79.1 or later.

## Is CVE-2020-26284 being exploited?

There is no known exploitation of CVE-2020-26284 in the wild and no public exploit code.

## Other vulnerabilities in gohugoio hugo

- [CVE-2026-75926](https://insights.sbomify.com/CVE-2026-75926/): Hugo 0.162.0 to 0.164.x - Node Permission Model Bypass via Default TailwindCSS Child-Process Grant (critical 9.3)
- [CVE-2026-100690](https://insights.sbomify.com/CVE-2026-100690/): Hugo v0.161.0 to v0.165.0 Arbitrary File Read via Symlinks (high 8.7)
- [CVE-2026-100692](https://insights.sbomify.com/CVE-2026-100692/): Hugo before v0.166.0 Path Traversal via Symlinked Mount Roots (high 8.7)
- [CVE-2026-100693](https://insights.sbomify.com/CVE-2026-100693/): Hugo v0.162.0 before v0.166.0 IP-literal Deny Rule Bypass (high 8.6)
- [CVE-2026-50135](https://insights.sbomify.com/CVE-2026-50135/): Hugo: Symlink confinement bypass in resources.Get (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26284 and fix it if it is affected.

What it is: CVE-2020-26284 is a high-severity command injection vulnerability in gohugoio hugo, published on 21 Dec 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-26284 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/gohugoio/hugo (Go): affected all versions; fixed in 0.79.1
- github.com/gohugoio/hugo (Go): affected all versions; fixed in 0.79.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-26284/ (Markdown: https://insights.sbomify.com/CVE-2020-26284/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26284
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26284
- OSV: https://osv.dev/vulnerability/CVE-2020-26284

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-26284/
Summaries are generated and may contain mistakes; the official description above is the record.