CVE-2026-44301Medium▾ SunlitHugo's Node tool execution allows file system access outside the project directory
▾ Sunlit zone — Low / medium · no exploitation signal
impact 27.5 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 25.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.3%
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.
From v0.161.0, Hugo runs Node tools under Node's permission model with strict defaults: No write access and only read access to the site source directories and files.
Block these tools in security.exec.allow.
github.com/gohugoio/hugo >= 0.43.0, < 0.161.0Upgrade to a patched release:
github.com/gohugoio/hugo 0.161.0Connected by shared product, vendor, weakness, or advisory.
CVE-2026-58404HighHugo: security.http.urls deny rules bypassed by alternate IPv4 encodings (SSRF)
CVE-2026-58402MediumHugo: XSS via unescaped code-fence language in default code block renderer
CVE-2026-35166MediumHugo: Certain markdown links are not properly escaped
CVE-2026-58403MediumHugo: Symlink confinement bypass in os.ReadFile
CVE-2020-26284High· 7.7Hugo can execute a binary from the current directory on Windows
CVE-2026-50133MediumHugo: XSS via text/html content files