cve.bz

CVE-2026-100690 gohugo hugo: Link Following

8.7 highEPSS 0.4%

High (8.7) in gohugo hugo. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

8.7 high
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

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-100690 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-100690?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-100690?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-100690 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
gohugoio hugofrom 0.161.0 before 0.166.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14hugo0.166.0-1DEBIAN-CVE-2026-100690
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morehugono fix listedUBUNTU-CVE-2026-100690
Red Hathummingbird:1hugo0:0.166.0-0.1.hum1RHSA-2026:66266

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because successful exploitation requires processing an untrusted project or pull request that specifically utilizes Node.js asset pipelines. Although an attacker could expose sensitive local files accessible to the builder by introducing malicious symlinks into the source tree, this flaw cannot be exploited remotely without direct user interaction or automated build triggers. Build systems and projects that only process trusted content or do not invoke Node.js asset transformations are not at risk.

Red Hat's mitigation

To mitigate this issue, implement the following operational controls:

1. Avoid processing untrusted pull requests, themes, or repository branches that execute Node.js transformation pipelines (such as PostCSS, TailwindCSS, or Babel). Builds that do not execute Node.js tools are unaffected.

2. Isolate Hugo builds inside dedicated containers or ephemeral sandboxes that have no sensitive host directories or files mounted, and run the build process with minimal privileges.

Caveat: Disabling or avoiding Node.js asset transformations may prevent custom stylesheets or scripts from compiling properly, which can alter the appearance or functionality of the generated site.

ProductPackageStateAdvisory
Cluster Observability Operator 1.5cluster-observability-operator/korrel8r-rhel9:1790854490Fixed 2026-10-01RHSA-2026:74609
Red Hat Hardened Imageshugo-main-0.166.0-0.1.hum1Fixed 2026-09-09RHSA-2026:66266
Red Hat Enterprise Linux 10grafanaNot affected
Red Hat Hardened Imagesgrafana12.4Not affected
Red Hat Hardened Imagesgrafana13.1Not affected
Red Hat Hardened Imagesgrafana13.2Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-rhel8Will not fix
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-rhel9Will not fix
Red Hat OpenStack Platform 18.0rhoso-operators/openstack-operator-bundleNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-100690.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON