Skip to main content
VulnerabilityPublished

CVE-2026-44301: gohugoio hugo · Path Traversal

Affects gohugoio hugoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.2 Medium : upgrade to 0.161.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.161.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade hugo and github.com/gohugoio/hugo to 0.161.0.

Affected software

ProductAffectedFixed in
gohugoiohugoAffected
  • >=0.43.0 <0.161.0
Fixed in
  • 0.161.0
Gogithub.com/gohugoio/hugopkg:golang/github.com/gohugoio/hugoOther threatsAffected
  • <0.161.0 >=0.43
Fixed in
  • 0.161.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Hugo to version 0.161.0 or later, where this vulnerability is fixed. Users who do not use PostCSS, Babel, or TailwindCSS, or only build trusted sites, are not affected and may not require immediate action. Patch status is confirmed fixed in version 0.161.0.

Description

Hugo is a static site generator. From 0.43 to before 0.161.0, when building a Hugo site that uses Node-based asset pipelines (PostCSS, Babel, TailwindCSS), Hugo invoked the configured Node tools without restrictions on file system access. As a result, executing hugo against an untrusted site could allow code running through these tools to read or write files outside the project's working directory. Users who do not use PostCSS, Babel, or TailwindCSS, or who only build trusted sites, are not affected. This vulnerability is fixed in 0.161.0.

References

Community reviews

Loading reviews…