SSRF (Server-Side Request Forgery) in github.com/gohugoio/hugo (CVE-2026-58404)
Summary
SSRF in github.com/gohugoio/hugo (CVE-2026-58404). Confidential information can be exposed externally. Mitigation: upgrade to 0.163.1 or later.
Original description
The description as published by the source.
Hugo is a static site generator. From v0.162.0 through v0.163.0, the default security.http.urls policy denies requests to loopback, internal, and cloud-metadata IPv4 literals, but the deny rule only matched dotted-decimal notation, so alternate IPv4 encodings of the same addresses, including integer, hex, or octal, passed the policy. When a template passes an untrusted or data-derived URL to resources.GetRemote and the host platform uses the cgo system resolver, these encodings resolve to the blocked address, allowing build-time server-side requests to loopback and internal services, including the cloud-metadata endpoint in hosted or CI builds; the same check is reused on redirects, so the gap also applies to each redirect hop. This issue is fixed in v0.163.1.
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-58404 has been found in github.com/gohugoio/hugo.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade github.com/gohugoio/hugo to 0.163.1 or later.
If unsure, ask your IT team or search "github.com/gohugoio/hugo CVE-2026-58404" on the vendor's site.
CVE-2026-58404 (github.com/gohugoio/hugo) — CWE-918 / CVSS v3 6.8
Attack vector: remote (network-reachable)
Patched: 0.163.1 — apply immediately
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.
SSRF (CWE-918) exists in github.com/gohugoio/hugo.
Check the vendor advisory for the affected versions of github.com/gohugoio/hugo.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 0.163.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade github.com/gohugoio/hugo to 0.163.1ステージング環境で 0.163.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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-58404 hugo Fixed in: 0.165.0-1
- Ubuntu UBUNTU-CVE-2026-58404 hugo
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com