CVE-2026-75926: Hugo 0.161.0 placed the Node asset pipelines behind the Node.js permission model so that code running through PostCSS…
CVE-2026-75926 · Severity: high · CVSS 8.6 · Published 2026-08-18
Hugo 0.161.0 placed the Node asset pipelines behind the Node.js permission model so that code running through PostCSS, Babel, or TailwindCSS could not reach the file system outside the project directory. Hugo 0.162.0 added tailwindcss to the AllowChildProcess default in config/security/securityConfig.go, which makes nodePermissionArgs in common/hexec/exec.go append --allow-child-process whenever the tool being launched is named tailwindcss. TailwindCSS loads the site's tailwind.config.js through require at startup, so top-level code in that file executes inside the permitted Node process and can call child_process to spawn a shell. The spawned process is not a Node process and inherits none of the permission flags, so it runs with the full privileges of the account performing the build. Building a site whose theme, module, or starter template supplies the Tailwind configuration therefore yields arbitrary command execution rather than the confined file access the permission model was introduced to enforce. Hugo 0.165.0 removes tailwindcss from the default security.exec.allow list, so the tool is no longer launched under the default configuration.
Quick answers
Is CVE-2026-75926 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-75926 being exploited in the wild.
How severe is CVE-2026-75926?
High severity, with a CVSS score of 8.6, published 18 August 2026.
Which products and versions are affected?
Gohugo Hugo. The advisory does not name versions.
Is there a fix for CVE-2026-75926?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-75926?
Check whether you run Gohugo Hugo. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.