---
id: CVE-2026-100690
title: >-
  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
summary: >-
  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 …
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'
cwe:
  - CWE-59
vendor: gohugoio
product: hugo
affected:
  - hugo >= 0.161.0 < 0.166.0
published: '2026-09-26'
updated: '2026-09-26'
sourceUpdated: '2026-09-26T14:16:53.560'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-100690'
references:
  - url: 'https://github.com/gohugoio/hugo/security/advisories/GHSA-x3mx-cm49-8m9c'
    label: disclosure@vulncheck.com
  - url: >-
      https://www.vulncheck.com/advisories/hugo-0.161.0-to-0.165.0-arbitrary-file-read-via-symlinks
    label: disclosure@vulncheck.com
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-26T13:33:20.906Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
