CVE-2026-58404: gohugoio hugo · Server-Side Request Forgery (SSRF)
Affects gohugoio hugoSource CVE Database V5
Not known to be exploited · CVSS 4.6 Medium : upgrade to 0.163.1 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.163.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 16 Nov 2026.
What to do
Upgrade gohugoio hugo to 0.163.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| gohugoiohugo | Affected
| Fixed in
|
Gogithub.com/gohugoio/hugopkg:golang/github.com/gohugoio/hugoOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Hugo version 0.163.1 or later, where this SSRF vulnerability is fixed. Until then, avoid passing untrusted or data-derived URLs to resources.GetRemote, especially on platforms using the cgo resolver. Patch status is not explicitly stated as 'official-fix' in the data, but the description confirms the issue is fixed in v0.163.1. Therefore, applying this update is the recommended remediation.
Description
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.
References
- github.com/gohugoio/hugo/security/advisories/GHSA-r46f-3rpw-hxrv (opens in a new tab)
- github.com/gohugoio/hugo/pull/15020 (opens in a new tab)
- github.com/gohugoio/hugo/commit/a00b5c72ac57afe26df6688ece3ca544a56df372 (opens in a new tab)
- github.com/gohugoio/hugo/releases/tag/v0.163.1 (opens in a new tab)