CVE-2026-44301: Hugo: Node tool execution allows file system access outside the project directory
Impact 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.
Patches 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.
Workarounds Block these tools in security.exec.allow.
Other sources
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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44301?
CVE-2026-44301 has a medium severity rating due to its potential to allow unauthorized file system access.
How do I fix CVE-2026-44301?
To fix CVE-2026-44301, upgrade Hugo to version 0.161.0 or later.
What types of configurations are impacted by CVE-2026-44301?
CVE-2026-44301 affects Hugo sites that use Node-based asset pipelines like PostCSS, Babel, and TailwindCSS.
How can CVE-2026-44301 affect untrusted sites?
CVE-2026-44301 can allow malicious code from untrusted sites to read or write files on the file system.
Which versions of Hugo are vulnerable to CVE-2026-44301?
Hugo versions between 0.43.0 and 0.161.0 are vulnerable to CVE-2026-44301.