Skip to main content
No exploitation reportedFix available

CVE-2026-100690

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

No exploitation reported by the sources we read.

  • Published2026-09-26
  • Fixed in0.166.0
  • WeaknessCWE-59

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-09-2614:16CVE publishedNVD

Versions per branch

NVD
Gohugo hugo
BranchAffectedFixed in
0.x≥ 0.161.0, < 0.166.00.166.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As VulnCheck, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • gohugoio hugoother versions: not affected
    Affected
    • ≥ 0.161.0, < 0.166.0fixed in 0.166.0semver

    Not affected = 0.166.0

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-09-26

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • hugoUbuntu:Pro:24.04:LTSall versions · no fixed version listed
  • hugoUbuntu:26.10all versions · no fixed version listed
  • hugoUbuntu:26.04:LTSall versions · no fixed version listed
  • hugoUbuntu:22.04:LTSall versions · no fixed version listed
  • hugoUbuntu:20.04:LTSall versions · no fixed version listed
  • hugoUbuntu:18.04:LTSall versions · no fixed version listed
  • hugoUbuntu:16.04:LTSall versions · no fixed version listed
  • hugoRed Hat:hummingbird:1all versions · fixed in 0:0.166.0-0.1.hum1

2 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-100690 Red Hat Product Security7 products fixed · 2 known affected

    github.com/gohugoio/hugo: Hugo: Arbitrary file read via symbolic link sandbox escape

    openshift-gitops-1/argocd-rhel8 as a component of Red Hat OpenShift GitOps · openshift-gitops-1/argocd-rhel9 as a component of Red Hat OpenShift GitOps

  • RHSA-2026:74609 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: Cluster Observability Operator 1.5.3

  • RHSA-2026:66266 Red Hat Product Security3 products fixed

    Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

Full record on NVD

Fix

  1. Update Gohugo hugo to 0.166.0
  2. Vendor fix Red Hat Product Security RHSA-2026:74609 · 4 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  3. Vendor fix Red Hat Product Security CVE-2026-100690 · 3 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
  4. Workaround from the vendor Red Hat Product Security RHSA-2026:74609 · 97 productsTo 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. Isol…
  5. No fix planned, says the vendor Red Hat Product Security CVE-2026-100690 · 2 productsWill not fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2026-09-30
  • CNACVSS 4.08.7known since 2026-10-23
  • CNACVSS 3.17.5known since 2026-10-23
  • CNAweakness (CWE)CWE-59known since 2026-10-23
  • FIRST EPSSEPSS score0.4 %2026-11-18
  • OSVaffected packages—
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 4.0 vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-09-26
Last Modified
2026-09-30
NVD status
Analyzed
GitHub Advisory
GHSA-gqg5-5gw3-54pq

Frequently asked questions

What is CVE-2026-100690?

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.

Is CVE-2026-100690 actively exploited?

Active exploitation of CVE-2026-100690 has not been confirmed. Its EPSS score was 0.4% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-100690?

CVE-2026-100690 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running github.com/gohugoio/hugo? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record