Path Traversal in github.com/gohugoio/hugo (CVE-2026-44301)
Summary
Path traversal in github.com/gohugoio/hugo (CVE-2026-44301). Confidential information can be exposed externally. Mitigation: upgrade to 0.161.0 or later.
Original description
The description as published by the source.
Hugo is a static site generator. From 0.43 to before 0.161.0, when building a Hugo site that uses Node-based asset pipelines (PostCSS, Babel, TailwindCSS), Hugo invoked the configured Node tools without restrictions on file system access. As a result, executing hugo against an untrusted site could allow code running through these tools to read or write files outside the project's working directory. Users who do not use PostCSS, Babel, or TailwindCSS, or who only build trusted sites, are not affected. This vulnerability is fixed in 0.161.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44301 has been found in github.com/gohugoio/hugo.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade github.com/gohugoio/hugo to 0.161.0 or later.
If unsure, ask your IT team or search "github.com/gohugoio/hugo CVE-2026-44301" on the vendor's site.
CVE-2026-44301 (github.com/gohugoio/hugo) — CWE-22 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.161.0 — apply immediately
Workaround: Block these tools in security.exec.allow.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/gohugoio/hugo.
Check the vendor advisory for the affected versions of github.com/gohugoio/hugo.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 0.161.0.
Workaround: Block these tools in security.exec.allow.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/gohugoio/hugo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/gohugoio/hugo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/gohugoio/hugoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Block these tools in [security.exec.allow](https://gohugo.io/configuration/security/).パッチが適用されるまでの応急処置として、Block these tools in security.exec.allow. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/gohugoio/hugo to 0.161.0ステージング環境で 0.161.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-44301 hugo
- Ubuntu UBUNTU-CVE-2026-44301 hugo
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com