CVE-2026-75926 gohugoio CVE debrief

Who should care

Defenders responsible for Hugo deployments, especially those using TailwindCSS, should assess exposure and prioritize remediation to prevent potential arbitrary command execution. This includes reviewing and restricting the use of TailwindCSS in Hugo projects, monitoring and auditing deployments for signs of exploitation, and verifying the Hugo version used. Security teams and operators managing Hugo sites should verify and apply patches, review compensing

Why it matters

Defenders should prioritize verifying and remediating this vulnerability in Hugo deployments, especially those using TailwindCSS, to prevent potential arbitrary command execution.

• Potential arbitrary command execution via TailwindCSS
• Bypass of Node asset pipelines permission model
• Elevation of privileges to the account performing the build
• Verification of Hugo version and TailwindCSS usage required

Technical summary

Hugo versions 0.162.0 to 0.164.0 are vulnerable to a permission bypass via TailwindCSS, allowing arbitrary command execution. The issue arises from the addition of tailwindcss to the AllowChildProcess default in config/security/securityConfig.go, which enables top-level code in tailwind.config.js to spawn a shell with full privileges. The vulnerability was fixed in Hugo 0.165.0 by removing tailwindcss from the default security.exec.allow list, thus preventing the arbitrary command execution and ensuring confined file access.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability in Hugo deployments, especially those using TailwindCSS, to prevent potential arbitrary command execution.

Recommended defensive actions

• Verify and apply the patch by updating to Hugo version 0.165.0 or later
• Review and restrict the use of TailwindCSS in Hugo projects
• Monitor and audit Hugo deployments for potential exploitation
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source references indicate that Hugo versions 0.162.0 to 0.164.0 are affected due to the addition of tailwindcss to the AllowChildProcess default in config/security/securityConfig.go, which allows arbitrary command execution. The issue was fixed in Hugo 0.165.0.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.