Hugo v0.161.0 to v0.165.0 Arbitrary File Read via Symlinks (CVE-2026-100690) | HOL Guard CVE

High · CVSS 8.7CVE-2026-100690

Hugo v0.161.0 to v0.165.0 Arbitrary File Read via Symlinks

Answer in brief

CVE-2026-100690 records a High severity (CVSS 8.7) vulnerability in Hugo v0.161.0 to v0.165.0 Arbitrary File Read via Symlinks. The current sources do not mark it as known exploited. The current feed maps gohugoio/hugo (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 26, 2026Updated Sep 26, 2026Source checked Sep 26, 2026First seen by HOL Sep 26, 2026Material review Sep 26, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.7
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps gohugoio/hugo (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
gohugoio/hugogeneric	>=0.161.0 <0.166.0	0.166.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for gohugoio/hugo.
Review the reported fix. Update gohugoio/hugo to 0.166.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 26, 2026

Sources and claim methodology

Upstream source description

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 point outside the allowed set, Hugo did not detect symlinks escaping the sandbox. An attacker who can contribute content to a Hugo project (for example via a pull request) can commit a symlink such as assets/css/x.css -> /etc/passwd together with a PostCSS plugin that reads it, allowing any file readable by the Hugo build process to be disclosed and potentially embedded in the published site. This affects builds using the default security configuration; projects that do not invoke Node.js tools are unaffected. Fixed in v0.166.0, which scans allowed paths and fails the build when a symbolic link resolves outside them.

Quoted source text, attributed separately from HOL analysis.