Back to feed
18Track

Hugo security.http.urls deny rules bypassed by alternate IPv4 encodings

gohugoio hugo · CVE-2026-58404
0 news outlets0 CERTs and agencies0 research labs

Assessment: Track

SSVC decision points: exploitation none, automatable no, technical impact partial, deployment low.

What is it?

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.

Evidence

Official warnings1National CERTs, government cyber security agencies and the vendor’s own advisories

Exploitation

  • Exploit code published (not verified by us)
  • Exploited in the wild (confirmed by a source)
  • Listed as known exploited (CISA KEV)
CVSS
4.6
EPSS
–
First seen
8 Jul 2026
Status
confirmed

All gohugoio vulnerabilities