cve.bz

CVE-2026-75926 gohugo hugo

9.3 criticalExploit referenceEPSS 0.2%Fix available

Critical (9.3) in gohugo hugo. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

9.3 critical
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

CVSS 3.1

8.6 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-08-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1188 Initialization of a Resource with an Insecure Default
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-75926 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-75926?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-75926?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-75926 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
gohugoio hugofrom 0.162.0 before 0.165.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14hugo0.165.0-1DEBIAN-CVE-2026-75926
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morehugono fix listedUBUNTU-CVE-2026-75926

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Critical.

Red Hat's statement

A command execution flaw rated Critical was found in Hugo, affecting the static site generator's Node.js asset-processing pipeline in versions 0.162.0 through 0.164.x. Hugo 0.161.0 placed its Node asset pipelines behind the Node.js permission model so that tools such as PostCSS, Babel, and TailwindCSS could not reach the file system outside the project directory. Hugo 0.162.0 then added tailwindcss to the default AllowChildProcess security configuration, and because TailwindCSS loads the site's tailwind.config.js through require at startup, top-level code in a Tailwind configuration supplied by a theme, module, or starter template 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 building a site with an untrusted Tailwind configuration results in arbitrary command execution with the full privileges of the account running the build, rather than the confined file access the permission model was introduced to enforce. Within Red Hat's product scope, only the Fedora community hugo package is affected, and a fix is being pursued for that community distribution. The hugo package shipped in Red Hat Hardened Images is not affected because the version shipped does not contain the vulnerable code. Upstream assesses this flaw as Critical with a CVSS 4.0 score of 9.3, while the Red Hat CVSS 3.1 vector scores it 8.6 (Important); this difference reflects the CVSS version and metrics used rather than the flaw's Red Hat impact rating of Critical.

Red Hat's mitigation

Remove tailwindcss from the security.exec.allow allowlist in the site configuration. In hugo.toml, set the [security.exec] allow list explicitly without tailwindcss, for example:

[security.exec]

allow = ['^(dart-)?sass$', '^go$', '^git$', '^node$', '^postcss$']

This prevents Hugo from launching the tailwindcss executable during builds, at the cost of TailwindCSS-based asset processing. Alternatively, only build sites whose themes, modules, and Tailwind configuration files come from trusted sources. Upstream Hugo 0.165.0 removes tailwindcss from the default security.exec.allow list, so upgrading to a version that includes this change also addresses the issue.

ProductPackageStateAdvisory
Red Hat Hardened ImageshugoNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-75926.

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON