Advisory record · GHSA-8j34-9876-pvfq

Hugo can execute a binary from the current directory on Windows

CVSS 7.7 HighEPSS 0.015 · 74th percentile

Published by the GitHub Advisory Database at 23 Jun 2021, 17:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/gohugoio/hugoGo<0.79.10.79.1
Identifiers
GHSA-8j34-9876-pvfq · CVE-2020-26284
Weakness (CWE)
CWE-78
Published
23 Jun 2021
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Hugo versions before 0.79.1 are vulnerable on Windows. If a malicious executable or batch file with the same name as a binary Hugo calls, such as for Pandoc rendering, sits in the current working directory when hugo runs, that file is run instead of the system program. Windows users who run hugo inside untrusted sites are affected, so upgrade to Hugo 0.79.1 or later.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.7 High 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.015, the 74th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:45 UTC First seen by agentprime
  2. 31 Oct 2026, 14:45 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.