File access outside build root via TailwindCSS
Published Sep 11, 2026 · Updated Sep 11, 2026
Improper permission restriction in Hugo after 0.43 and before 0.165.0 allows attackers to read or write files outside the build root via TailwindCSS. Hugo's default security.exec.allow list launches TailwindCSS while Node receives addon, child-process, and worker permissions that defeat the intended file-system boundary. Exposure requires a build of an untrusted site that uses TailwindCSS; successful access is limited by the build account's file permissions.
Summary
What happened
Improper permission restriction in Hugo after 0.43 and before 0.165.0 allows attackers to read or write files outside the build root via TailwindCSS. Hugo's default security.exec.allow list launches TailwindCSS while Node receives addon, child-process, and worker permissions that defeat the intended file-system boundary. Exposure requires a build of an untrusted site that uses TailwindCSS; successful access is limited by the build account's file permissions.
The record
- CVE
- CVE-2026-89259
- Published
- Sep 11, 2026
- Updated
- Sep 11, 2026
- Vendor
- Hugo Authors
- Product
- Hugo
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 11, 2026CVE publishedPublication date reported by the CVE source.
- Sep 11, 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 <0.165.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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