Skip to main content
VulnerabilityPublished Updated

CVE-2026-75926: gohugoio hugo · Insecure Default

Affects gohugoio hugoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 0.165.0 as a priority.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.165.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade gohugoio hugo to 0.165.0.

Affected software

ProductAffectedFixed in
gohugoiohugoAffected
  • >=0.162.0 <0.165.0
Fixed in
  • 0.165.0
GitHubhugopkg:github/hugoOther threatsAffected
  • >=0.162.0 <0.165.0
Fixed in
  • 0.165.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Hugo to version 0.165.0 or later, where TailwindCSS is no longer launched with the --allow-child-process flag by default, eliminating this insecure permission. Until upgrading, avoid building sites that include untrusted TailwindCSS configurations or disable TailwindCSS in the build process. Patch status is confirmed fixed in Hugo 0.165.0.

Description

A critical vulnerability (CVE-2026-75926) in Hugo versions 0.162.0 through 0.164.x allows arbitrary command execution due to insecure default permissions when running TailwindCSS. The vulnerability arises because TailwindCSS is launched with --allow-child-process permission, enabling code in tailwind.config.js to spawn shell processes with full user privileges. This breaks the intended Node.js permission confinement introduced in Hugo 0.161.0. The issue is fixed in Hugo 0.165.0 by removing TailwindCSS from the default allowed child process list.

References

Community reviews

Loading reviews…