CVE-2026-75926

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

Score 8.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-18. A secondary CVSS source baseline 8.6; sources differ by 0.0.

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

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

Hugo 0.161.0 placed the Node asset pipelines behind the Node.js permission model so that code running through PostCSS, Babel, or TailwindCSS could not reach the file system outside the project directory. Hugo 0.162.0 added tailwindcss to the AllowChildProcess default in config/security/securityConfig.go, which makes nodePermissionArgs in common/hexec/exec.go append --allow-child-process whenever the tool being launched is named tailwindcss. TailwindCSS loads the site's tailwind.config.js through require at startup, so top-level code in that file executes inside the permitted Node process and can call child_process to spawn a shell. The spawned process is not a Node process and inherits none of the permission flags, so it runs with the full privileges of the account performing the build. Building a site whose theme, module, or starter template supplies the Tailwind configuration therefore yields arbitrary command execution rather than the confined file access the permission model was introduced to enforce. Hugo 0.165.0 removes tailwindcss from the default security.exec.allow list, so the tool is no longer launched under the default configuration.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
39
EG Risk 39/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
Severity86% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

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

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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

August 18, 2026

Last Modified

September 29, 2026

Advisory Details (6)

Auto-updated Aug 18, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github.
generic

Hugo 0.162.0 to 0.164.x - Node Permission Model Bypass via Default TailwindCSS Child-Process Grant | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hugo-to-x-node-permission-model-bypass-via-default-tailwindcss-child-process-grant
generic

GitHub - gohugoio/hugo: The world’s fastest framework for building websites. · GitHub

https://github.com/gohugoio/hugo
generic

hugo/common/hexec/exec.go at v0.164.0 · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/blob/v0.164.0/common/hexec/exec.go#L292-L295
github

hugo/config/security/securityConfig.go at v0.164.0 · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/blob/v0.164.0/config/security/securityConfig.go#L72-L79
generic

Remove tailwindcss from the default security.exec.allow list · Issue #15178 · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/issues/15178
github_commit

commit 8a55df7af2e6 (gohugoio/hugo)

Fix landed in gohugoio/hugo commit 8a55df7af2e6 — awaiting tagged release

https://github.com/gohugoio/hugo/commit/8a55df7af2e6da31297245cc54fa2e3b521d93e8

Vendor Advisories for CVE-2026-75926(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
hugo0.131.0-1 ... 0.162.1-7 (43 versions)
  • every version up to 0.165.0-1: fixed in 0.165.0-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 108× 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.

Showing the most recent 100 of 188 total refreshes for this CVE.

  1. 2026-10-05 06:06 UTCEG score recompute
  2. 2026-10-05 06:06 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 16:23 UTCGHSA enrichment
  5. 2026-10-04 05:18 UTCGHSA enrichment
  6. 2026-10-03 17:39 UTCEG score recompute
  7. 2026-10-03 17:39 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 02:44 UTCEG score recompute
  10. 2026-10-03 02:44 UTCGHSA enrichment
  11. 2026-10-02 15:38 UTCGHSA enrichment
  12. 2026-10-02 01:28 UTCEG score recompute
  13. 2026-10-02 01:28 UTCGHSA enrichment
  14. 2026-10-01 19:50 UTCEPSS rescore
  15. 2026-10-01 10:11 UTCGHSA enrichment
  16. 2026-09-30 23:05 UTCEG score recompute
  17. 2026-09-30 23:05 UTCGHSA enrichment
  18. 2026-09-30 11:57 UTCGHSA enrichment
  19. 2026-09-29 23:38 UTCEG score recompute
  20. 2026-09-29 23:37 UTCGHSA enrichment
  21. 2026-09-29 15:24 UTCEPSS rescore
  22. 2026-09-28 21:56 UTCEG score recompute
  23. 2026-09-28 21:56 UTCGHSA enrichment
  24. 2026-09-28 13:52 UTCEPSS rescore
  25. 2026-09-28 06:08 UTCGHSA enrichment
Show 75 more
  1. 2026-09-27 19:02 UTCEG score recompute
  2. 2026-09-27 19:02 UTCGHSA enrichment
  3. 2026-09-27 13:48 UTCEPSS rescore
  4. 2026-09-27 07:57 UTCEG score recompute
  5. 2026-09-27 07:57 UTCGHSA enrichment
  6. 2026-09-26 15:59 UTCEPSS rescore
  7. 2026-09-26 00:28 UTCEPSS rescore
  8. 2026-09-25 07:22 UTCGHSA enrichment
  9. 2026-09-24 20:16 UTCEG score recompute
  10. 2026-09-24 20:16 UTCGHSA enrichment
  11. 2026-09-24 14:59 UTCEG score recompute
  12. 2026-09-24 14:59 UTCGHSA enrichment
  13. 2026-09-24 14:04 UTCEPSS rescore
  14. 2026-09-24 07:26 UTCGHSA enrichment
  15. 2026-09-23 20:20 UTCEG score recompute
  16. 2026-09-23 20:20 UTCGHSA enrichment
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-23 07:33 UTCGHSA enrichment
  19. 2026-09-22 20:27 UTCEG score recompute
  20. 2026-09-22 20:27 UTCGHSA enrichment
  21. 2026-09-22 16:01 UTCEPSS rescore
  22. 2026-09-22 06:24 UTCEG score recompute
  23. 2026-09-22 06:24 UTCGHSA enrichment
  24. 2026-09-21 21:09 UTCEPSS rescore
  25. 2026-09-21 19:18 UTCGHSA enrichment
  26. 2026-09-21 08:12 UTCGHSA enrichment
  27. 2026-09-20 20:46 UTCEG score recompute
  28. 2026-09-20 20:46 UTCGHSA enrichment
  29. 2026-09-20 20:16 UTCEPSS rescore
  30. 2026-09-20 09:40 UTCGHSA enrichment
  31. 2026-09-19 22:02 UTCEG score recompute
  32. 2026-09-19 22:01 UTCGHSA enrichment
  33. 2026-09-19 10:54 UTCGHSA enrichment
  34. 2026-09-18 21:51 UTCEG score recompute
  35. 2026-09-18 21:51 UTCGHSA enrichment
  36. 2026-09-18 19:28 UTCEPSS rescore
  37. 2026-09-18 08:57 UTCGHSA enrichment
  38. 2026-09-17 21:51 UTCEG score recompute
  39. 2026-09-17 21:51 UTCGHSA enrichment
  40. 2026-09-17 09:04 UTCGHSA enrichment
  41. 2026-09-16 21:57 UTCEG score recompute
  42. 2026-09-16 21:57 UTCGHSA enrichment
  43. 2026-09-16 14:08 UTCEPSS rescore
  44. 2026-09-16 06:14 UTCEG score recompute
  45. 2026-09-16 06:14 UTCGHSA enrichment
  46. 2026-09-16 05:15 UTCEPSS rescore
  47. 2026-09-15 19:09 UTCGHSA enrichment
  48. 2026-09-15 06:50 UTCEG score recompute
  49. 2026-09-15 06:50 UTCGHSA enrichment
  50. 2026-09-15 03:12 UTCEPSS rescore
  51. 2026-09-14 19:44 UTCGHSA enrichment
  52. 2026-09-14 07:53 UTCGHSA enrichment
  53. 2026-09-13 20:48 UTCEG score recompute
  54. 2026-09-13 20:48 UTCGHSA enrichment
  55. 2026-09-13 09:42 UTCGHSA enrichment
  56. 2026-09-12 22:36 UTCEG score recompute
  57. 2026-09-12 22:36 UTCGHSA enrichment
  58. 2026-09-12 15:02 UTCEPSS rescore
  59. 2026-09-12 11:30 UTCGHSA enrichment
  60. 2026-09-12 00:20 UTCEG score recompute
  61. 2026-09-12 00:20 UTCGHSA enrichment
  62. 2026-09-11 14:53 UTCEPSS rescore
  63. 2026-09-11 13:14 UTCEG score recompute
  64. 2026-09-11 13:14 UTCGHSA enrichment
  65. 2026-09-11 00:39 UTCGHSA enrichment
  66. 2026-09-10 13:24 UTCEG score recompute
  67. 2026-09-10 13:24 UTCGHSA enrichment
  68. 2026-09-10 09:35 UTCEPSS rescore
  69. 2026-09-10 02:18 UTCGHSA enrichment
  70. 2026-09-09 15:12 UTCGHSA enrichment
  71. 2026-09-09 03:26 UTCEG score recompute
  72. 2026-09-09 03:26 UTCGHSA enrichment
  73. 2026-09-08 22:01 UTCEPSS rescore
  74. 2026-09-08 03:14 UTCGHSA enrichment
  75. 2026-09-07 16:08 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-75926?
CVE-2026-75926 is a high vulnerability published on August 18, 2026. Hugo 0.161.0 placed the Node asset pipelines behind the Node.js permission model so that code running through PostCSS, Babel, or TailwindCSS could not reach the file system outside the project directory. Hugo 0.162.0 added tailwindcss to the AllowChildProcess default in…
When was CVE-2026-75926 disclosed?
CVE-2026-75926 was first published on August 18, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75926 actively exploited?
CVE-2026-75926 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75926?
CVE-2026-75926 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-75926?
An upstream fix for CVE-2026-75926 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-75926 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-75926

Explore →

Is Your Infrastructure Affected by CVE-2026-75926?

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

Book a Demo →Browse All CVEs