CVE-2026-100690

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-26. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
Patch available. Sources: github.
generic

Hugo v0.161.0 to v0.165.0 Arbitrary File Read via Symlinks | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hugo-0.161.0-to-0.165.0-arbitrary-file-read-via-symlinks
github Patch Available

Arbitrary file read via symlinks bypassing the Node.js permission model in css.PostCSS and other Node.js tools · Advisory · gohugoio/hugo · GitHub

Affected: v0.166.0. Before a Node.js tool is invoked, Hugo now scans the allowed paths and

https://github.com/gohugoio/hugo/security/advisories/GHSA-x3mx-cm49-8m9c

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcluster-observability-operator/korrel8r-rhel9:17908544902026-10-01redhat
redhathugo-main-0.166.0-0.1.hum12026-09-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 45× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 07:48 UTCVendor advisory
  2. 2026-10-04 07:48 UTCGHSA enrichment
  3. 2026-10-03 19:20 UTCEG score recompute
  4. 2026-10-03 19:20 UTCVendor advisory
  5. 2026-10-03 19:20 UTCGHSA enrichment
  6. 2026-10-03 14:25 UTCEPSS rescore
  7. 2026-10-03 06:51 UTCVendor advisory
  8. 2026-10-03 06:51 UTCGHSA enrichment
  9. 2026-10-02 18:22 UTCVendor advisory
  10. 2026-10-02 18:22 UTCGHSA enrichment
  11. 2026-10-02 18:22 UTCEG score recompute
  12. 2026-10-02 18:22 UTCVendor advisory
  13. 2026-10-02 18:22 UTCGHSA enrichment
  14. 2026-10-02 05:54 UTCEG score recompute
  15. 2026-10-02 05:54 UTCVendor advisory
  16. 2026-10-02 05:54 UTCGHSA enrichment
  17. 2026-10-01 19:49 UTCEPSS rescore
  18. 2026-10-01 17:26 UTCVendor advisory
  19. 2026-10-01 17:26 UTCGHSA enrichment
  20. 2026-10-01 04:57 UTCVendor advisory
  21. 2026-10-01 04:57 UTCGHSA enrichment
  22. 2026-09-30 16:27 UTCEG score recompute
  23. 2026-09-30 16:27 UTCVendor advisory
  24. 2026-09-30 16:27 UTCGHSA enrichment
  25. 2026-09-30 15:31 UTCEG score recompute
Show 25 more
  1. 2026-09-30 15:31 UTCVendor advisory
  2. 2026-09-30 15:31 UTCGHSA enrichment
  3. 2026-09-30 15:02 UTCEPSS rescore
  4. 2026-09-30 07:51 UTCVendor advisory
  5. 2026-09-30 07:51 UTCGHSA enrichment
  6. 2026-09-29 19:22 UTCVendor advisory
  7. 2026-09-29 19:22 UTCGHSA enrichment
  8. 2026-09-29 18:14 UTCEG score recompute
  9. 2026-09-29 18:14 UTCVendor advisory
  10. 2026-09-29 18:13 UTCGHSA enrichment
  11. 2026-09-29 15:20 UTCEPSS rescore
  12. 2026-09-29 05:26 UTCEG score recompute
  13. 2026-09-29 05:26 UTCGHSA enrichment
  14. 2026-09-28 16:58 UTCGHSA enrichment
  15. 2026-09-28 16:29 UTCEG score recompute
  16. 2026-09-28 16:29 UTCGHSA enrichment
  17. 2026-09-28 13:50 UTCEPSS rescore
  18. 2026-09-28 04:00 UTCGHSA enrichment
  19. 2026-09-27 15:31 UTCEG score recompute
  20. 2026-09-27 15:31 UTCGHSA enrichment
  21. 2026-09-27 03:00 UTCEG score recompute
  22. 2026-09-27 03:00 UTCGHSA enrichment
  23. 2026-09-26 14:31 UTCEG score recompute
  24. 2026-09-26 13:35 UTCEG score recompute
  25. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-100690?
CVE-2026-100690 is a high vulnerability published on September 26, 2026. 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…
When was CVE-2026-100690 disclosed?
CVE-2026-100690 was first published on September 26, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100690 actively exploited?
CVE-2026-100690 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100690?
CVE-2026-100690 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100690?
A fix for CVE-2026-100690 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100690 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-100690

Explore →

Is Your Infrastructure Affected by CVE-2026-100690?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.