Skip to main content
No exploitation reportedFix available

CVE-2026-100692

Hugo before v0.166.0 Path Traversal via Symlinked Mount Roots

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

Timeline

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

Versions per branch

NVD
Gohugo hugo
BranchAffectedFixed in
0.x≥ 0.123.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.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

3 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-100692 Red Hat Product Security3 products fixed · 1 known affected

    github.com/gohugoio/hugo: Hugo: Information disclosure via symlinked mount roots

    grafana.src as a component of Red Hat Enterprise Linux 10

  • 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 CVE-2026-100692 · 3 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
  3. Workaround from the vendor Red Hat Product Security CVE-2026-100692 · 4 productsInspect checked-in themes and vendored modules for symlinks at mount roots before building. Build untrusted content in an isolated environment without access to sensitive host files.
  4. No fix available, says the vendor Red Hat Product Security CVE-2026-100692 · 1 productFix deferred

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-28
  • 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-29
NVD status
Analyzed
GitHub Advisory
GHSA-m29q-9cm9-wcf6

Frequently asked questions

What is CVE-2026-100692?

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.

Is CVE-2026-100692 actively exploited?

Active exploitation of CVE-2026-100692 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-100692?

CVE-2026-100692 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