CVE-2026-75926: Hugo 0.161.0 placed the Node asset pipelines behind the Node.js permission model so that code running through

This month

HIGH 8.6UPGRADE

CVE-2026-75926 is a high-severity flaw (CVSS 8.6) affecting hugo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.6 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-1188
Published	2026-08-18
Last modified	2026-10-22

Publisher (CNA): VulnCheck · Vendor: gohugo

Last updated 2026-10-22 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-08-18Published CVE record published
2026-10-22 22:10 UTCUpdated Record last modified

gohugo hugo UPGRADE

Affected: >= 0.162.0 and < 0.165.0

Fixed in: 0.165.0

Safe to downgrade to: a release before 0.162.0

1. Check installed version

apt-cache policy hugo || rpm -q hugo || hugo --version

2. UPGRADE to 0.165.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade hugo

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade hugo

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 0.162.0 (Debian / Ubuntu)

apt-cache madison hugo sudo apt install hugo=<VERSION_BEFORE_0.162.0> sudo apt-mark hold hugo

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list hugo sudo dnf downgrade hugo-<VERSION_BEFORE_0.162.0> sudo dnf versionlock add hugo

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Fedora 46 · retext · FIXED · 8.1.0-1.fc46 · FEDORA-2026-0602a84203 · source

sudo dnf upgrade --advisory=FEDORA-2026-0602a84203

Debian 12 · hugo · NOT AFFECTED

Debian 13 · hugo · NOT AFFECTED

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-75926?

hugo: upgrade to 0.165.0. Exact commands for each OS are on this page.

Is CVE-2026-75926 being exploited?

CVE-2026-75926 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-75926 affect?

CVE-2026-75926 affects hugo. Severity is high (CVSS 8.6). 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 th

How urgent is CVE-2026-75926?

Priority 40/100. High severity; Public exploit reference

Software pages

Node.js vulnerabilities

Related CVEs

CVE-2026-35166 MEDIUM 5.4 UPGRADE UPGRADE Hugo is a static site generator

References

← Back to latest CVEs