# CVE-2026-10582: Hugo 0.91.0 through 0.165.0 Server-Side Request Forgery via security.http.urls Lacking Destination Address Validation

> Attackers can exploit Hugo's URL allowlist bypass to fetch internal resources via SSRF, leaking sensitive data into generated site artifacts.

- **Severity:** High 8.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-10582, GHSA-wg2f-v5x6-m39r, UBUNTU-CVE-2026-10582

## What is CVE-2026-10582?

CVE-2026-10582 is a high-severity server-side request forgery vulnerability in gohugoio hugo, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-10582?


## How do I fix CVE-2026-10582?

Upgrade to a fixed version.

## Is CVE-2026-10582 being exploited?

There is no known exploitation of CVE-2026-10582 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10582 and fix it if it is affected.

What it is: CVE-2026-10582 is a high-severity server-side request forgery vulnerability in gohugoio hugo, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-10582 in the wild and no public exploit code.

Affected product: gohugoio hugo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10582/ (Markdown: https://insights.sbomify.com/CVE-2026-10582/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10582
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10582
- OSV: https://osv.dev/vulnerability/CVE-2026-10582

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10582/
Summaries are generated and may contain mistakes; the official description above is the record.