Server-Side Request Forgery (SSRF) Affecting hugo package, versions *


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.32% (24th 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-DEBIANUNSTABLE-HUGO-19270623
  • published27 Aug 2026
  • disclosed24 Aug 2026

Introduced: 24 Aug 2026

NewCVE-2026-10582  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

There is no fixed version for Debian:unstable hugo.

NVD Description

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

Hugo's security.http.urls allowlist is the only control on outbound fetches made by resources.GetRemote, and it inspects the URL text alone. CheckAllowedHTTPURL in config/security/securityConfig.go applies the configured pattern list and then re-checks a canonicalised form of an integer, hex or octal IPv4 host, but it never resolves the hostname and never inspects the address the HTTP client actually connects to. The client constructed in resources/resource_factories/create/create.go installs no dial-time hook, so no check occurs at connection time either. A hostname that resolves to a loopback, private or cloud-metadata address therefore satisfies the policy, and the response body is embedded in the generated site. An attacker who can supply a URL through content, for example a front-matter field or a CMS field, can make the build fetch an internal endpoint and publish the response in the static output, so the build artifact itself carries the data out.

CVSS Base Scores

version 3.1