cve.bz

CVE-2026-10582 gohugoio hugo: SSRF

8.3 highEPSS 0.4%

High (8.3) in gohugoio hugo. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

8.3 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-10582 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-10582?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-10582?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-10582 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
gohugoio hugofrom 0.91.0 through 0.165.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13hugono fix listedDEBIAN-CVE-2026-10582
Debian14hugo0.166.0-1DEBIAN-CVE-2026-10582
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morehugono fix listedUBUNTU-CVE-2026-10582
Red Hathummingbird:1hugo0:0.166.0-0.1.hum1RHSA-2026:66266

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity because an attacker who can inject content into the site generation pipeline can force the build environment to query sensitive internal services and leak confidential responses into publicly distributed build artifacts. In typical Red Hat environments, Hugo is used within automated CI/CD pipelines and containerized documentation workflows where build workers often operate inside protected internal networks or cloud environments with access to metadata services. Exploitation requires the ability to supply or modify content fields that trigger remote resource fetching, meaning environments that build only fully trusted, internally vetted repositories have significantly lower exposure.

Red Hat's mitigation

To mitigate this vulnerability, ensure that the Hugo `security.http.urls` allowlist is strictly configured to permit outbound requests only to explicitly trusted external domains. Implement network egress filtering to prevent Hugo from initiating connections to internal, loopback, or private IP address ranges. This can be achieved by configuring firewall rules or network policies to block outbound traffic from the Hugo environment to RFC1918 addresses and other internal network segments.

ProductPackageStateAdvisory
Red Hat Hardened Imageshugo-main-0.166.0-0.1.hum1Fixed 2026-09-09RHSA-2026:66266
Red Hat Hardened Imagesgrafana12.4Not affected
Red Hat Hardened Imagesgrafana13.1Not affected
Red Hat Hardened Imagesgrafana13.2Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-rhel8Not affected
Red Hat OpenShift GitOpsopenshift-gitops-1/argocd-rhel9Not affected
Red Hat OpenStack Platform 18.0rhoso-operators/openstack-operator-bundleNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-10582.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON