CVE-2026-100692
Hugo is a static site generator
- Risk score
- 57/100
- CVSS
- 7.5 v3.1
- Exploit chance (30 days)
- 0.4%
- Published
- 26 Sep 2026
Open in the live forecast Today's forecast
What to know
- What it is
- Hugo is a static site generator. In versions after v0.123.0 and before v0.166.0, Hugo's symlink confinement checks stopped at the mount root itself, so a theme or module checked into themes/ (or a vendored module) could contain a symlink at a mount root (for example themes/mytheme/assets -> /some/dir/outside). Files b…
- Affected
- Gohugo Hugo before 0.166.0
- Fix
- Upgrade Gohugo Hugo to 0.166.0 or later.
- Exploitation
- No known exploitation
Story map
At a glance
Gohugo Hugo: Amber, patch this week. Hugo versions from v0.161.0 through v0.165.0 run Node.js tools (css.PostCSS, css.TailwindCSS, js.Babel) under the Node.js permission model to restrict file system reads to the project directory and configured mounts. Because the Node.js permission model validates only the lexical path and follows symbolic links that p…
The flaws
- CVE-2026-100692: Hugo is a static site generator (CVSS 7.5 · EPSS 0%)
- CVE-2026-100690: Information disclosure (CVSS 7.5 · EPSS 0%)
- CVE-2026-100693: Hugo versions from v0.162.0 before v0.166.0 contain a case-sensitive validation flaw in the… (CVSS 8.4 · EPSS 0%)
The fix
Upgrade Gohugo Hugo: 0.166.0 or later on your release line
Who is exposed: Gohugo Hugo before 0.166.0
Where it stands
- No known exploitation
Connects to
- Same weakness: CWE-59 (CWE-59). 77 other warnings in 30 days
- Same product: Earlier Gohugo Hugo warnings. 2 in the last 90 days
Why it is Yellow
- CVSS 7.5 high
- Remotely exploitable without logging in
References
Original description
Hugo is a static site generator. In versions after v0.123.0 and before v0.166.0, Hugo's symlink confinement checks stopped at the mount root itself, so a theme or module checked into themes/ (or a vendored module) could contain a symlink at a mount root (for example themes/mytheme/assets -> /some/dir/outside). Files behind such a symlink were readable during a site build through resources.Get, resources.Match and similar functions, and could be published to public/ via static mounts, bypassing the rule that theme and module mount sources must be local paths. Modules fetched via Go modules are not affected because Go module zips cannot contain symlinks, and this is not an escalation for the main project, which may already mount absolute paths by configuration. Fixed in v0.166.0, where symlinked mount roots and symlinked directories between the mount root and the module directory are treated as non-existent for all modules. As a workaround, inspect themes/ and vendored modules for symlinks at mount roots before building, or replace symlinks with explicit mounts.
Last activity 26 Sep 2026. Patch Forecast updates every hour.