CVE-2026-100690
HIGHDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 26% of all known CVEs.
References
Related Vulnerabilities
Other CWE-59 (Link Following) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-30333 | High | 7.5 | 99% | KEV + Ransom | Fix |
| CVE-2021-21300 | High | 8.0 | 89% | - | Fix |
| CVE-2021-32610 | High | 7.1 | 73% | - | Fix |
| CVE-2020-36193 | High | 7.5 | 71% | KEV | Fix |
| CVE-2023-40028 | Medium | 4.9 | 69% | - | Fix |
| CVE-2024-57728 | High | 7.2 | 65% | KEV + Ransom | Fix |
Common questions
How do I fix CVE-2026-100690?
Published advisories record a fix for 2 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-100690 being actively exploited?
Not that we know of. CVE-2026-100690 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.35% is the estimated probability that it will be exploited in the next 30 days. That is higher than 26% of all scored CVEs.
How severe is CVE-2026-100690?
CVE-2026-100690 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-100690 affect?
Published advisories record a fix for hugo (Debian), Hugo (Windows application). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-100690
Markdown
[](https://tridentstack.com/cve/CVE-2026-100690)HTML
<a href="https://tridentstack.com/cve/CVE-2026-100690"><img src="https://tridentstack.com/cve/badge/CVE-2026-100690.svg" alt="CVE-2026-100690"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-30.