# CVE-2026-100692: Hugo before v0.166.0 Path Traversal via Symlinked Mount Roots

> A malicious theme or module can use symlinks to read and publish files outside the project directory during site builds.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-100692, GHSA-797m-7j5g-3rpr, GHSA-m29q-9cm9-wcf6, MINI-gjrf-rmgm-x3hc, MINI-wch8-gq35-82j4, UBUNTU-CVE-2026-100692

## What is CVE-2026-100692?

CVE-2026-100692 is a high-severity path traversal vulnerability in gohugoio hugo, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-100692?

It affects 1 product.


Products: Gohugo Hugo.

## How do I fix CVE-2026-100692?

Upgrade to a fixed version.

## Is CVE-2026-100692 being exploited?

There is no known exploitation of CVE-2026-100692 in the wild and no public exploit code.

## Other vulnerabilities in gohugoio hugo

- [CVE-2026-75926](https://insights.sbomify.com/CVE-2026-75926/): Hugo 0.162.0 to 0.164.x - Node Permission Model Bypass via Default TailwindCSS Child-Process Grant (critical 9.3)
- [CVE-2026-100690](https://insights.sbomify.com/CVE-2026-100690/): Hugo v0.161.0 to v0.165.0 Arbitrary File Read via Symlinks (high 8.7)
- [CVE-2026-100693](https://insights.sbomify.com/CVE-2026-100693/): Hugo v0.162.0 before v0.166.0 IP-literal Deny Rule Bypass (high 8.6)
- [CVE-2020-26284](https://insights.sbomify.com/CVE-2020-26284/): Hugo can execute a binary from the current directory on Windows (high 7.7)
- [CVE-2026-50135](https://insights.sbomify.com/CVE-2026-50135/): Hugo: Symlink confinement bypass in resources.Get (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100692 and fix it if it is affected.

What it is: CVE-2026-100692 is a high-severity path traversal vulnerability in gohugoio hugo, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100692 in the wild and no public exploit code.

Affected product: gohugoio hugo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100692/ (Markdown: https://insights.sbomify.com/CVE-2026-100692/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100692
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100692
- OSV: https://osv.dev/vulnerability/CVE-2026-100692

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100692/
Summaries are generated and may contain mistakes; the official description above is the record.