Server-Side Request Forgery (SSRF) Affecting hugo package, versions <0:0.163.3-0.1.hum1


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.37% (30th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-HUGO-18382271
  • published29 Jul 2026
  • disclosed6 Jul 2026

Introduced: 6 Jul 2026

CVE-2026-58404  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade RHEL:10 hugo to version 0:0.163.3-0.1.hum1 or higher.
This issue was patched in RHSA-2026:36862.

NVD Description

Note: Versions mentioned in the description apply only to the upstream hugo package and not the hugo package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1