Build-host command execution via Tailwind config
Published Aug 18, 2026 · Updated Aug 20, 2026
Command execution in Hugo 0.162.0 through 0.164.x allows attackers to run build-host commands via a crafted TailwindCSS configuration. In common/hexec/exec.go, nodePermissionArgs appends --allow-child-process for tools listed in AllowChildProcess, and config/security/securityConfig.go includes tailwindcss in that default list; because TailwindCSS loads tailwind.config.js with require, attacker-controlled top-level JavaScript can invoke child_process to spawn an unrestricted shell. Exploitation requires building an untrusted site, theme, module, or starter template that uses TailwindCSS, and the spawned process runs with the full privileges of the account performing the build.
Summary
What happened
Command execution in Hugo 0.162.0 through 0.164.x allows attackers to run build-host commands via a crafted TailwindCSS configuration. In common/hexec/exec.go, nodePermissionArgs appends --allow-child-process for tools listed in AllowChildProcess, and config/security/securityConfig.go includes tailwindcss in that default list; because TailwindCSS loads tailwind.config.js with require, attacker-controlled top-level JavaScript can invoke child_process to spawn an unrestricted shell. Exploitation requires building an untrusted site, theme, module, or starter template that uses TailwindCSS, and the spawned process runs with the full privileges of the account performing the build.
The record
- CVE
- CVE-2026-75926
- Published
- Aug 18, 2026
- Updated
- Aug 20, 2026
- Vendor
- Hugo Authors
- Product
- Hugo
- Classifications
- CWE-1188, T1059
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.162.0 <0.165.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo