CVE-2026-89259: critical vulnerability in gohugoio hugo
Hugo before v0.165.0 Insufficient Permission Restriction via TailwindCSS
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.3epss 0.6%
Hugo is a static site generator. From v0.161.0, Hugo executes Node tools under Node's permission model, but TailwindCSS — included in the default security.exec.allow list — requires a highly permissive configuration (--allow-addons, --allow-child-process, --allow-worker). As a result, the restrictions intended by the fix for GHSA-x597-9fr4-5857 could still be bypassed, allowing a Node tool invoked during a build to read and write files outside the project's working directory. Affected versions are those after v0.43; the issue was fixed in v0.165.0 by removing tailwindcss from the default security.exec.allow list. Users who do not use TailwindCSS, or who only build trusted sites, are not affected. As a workaround, users can define a restrictive security.exec.allow list in hugo.toml.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Affected products
gohugoio · hugoRelated CVEs — gohugoio hugo
In the same product, most dangerous first.
CVE-2020-26284HIGHHugo can execute a binary from the current directory on WindowsEPSS 1.5%CVE-2024-55601MEDIUMHugo does not escape some attributes in internal templatesEPSS 0.6%CVE-2024-32875MEDIUMHugo doesn't escape markdown title in internal render hooksEPSS 0.5%CVE-2026-58403MEDIUMHugo symlink confinement bypass in os.ReadFileEPSS 0.5%CVE-2026-89258CRITICALHugo before v0.165.0 Symlink Confinement Bypass via resources.GetEPSS 0.5%CVE-2026-10582HIGHHugo 0.91.0 through 0.165.0 Server-Side Request Forgery via security.http.urls Lacking Destination Address ValidationEPSS 0.4%