UBUNTU-CVE-2026-10582 (CVE-2026-10582)
Vulnerability from osv_ubuntu – Published: 2026-08-24 11:16 – Updated: 2026-10-17 09:37 – Source websiteHugo'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.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "golang-github-spf13-hugo-dev",
"binary_version": "0.15+git20160206.203.ed23711-1"
},
{
"binary_name": "hugo",
"binary_version": "0.15+git20160206.203.ed23711-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "hugo",
"purl": "pkg:deb/ubuntu/hugo@0.15+git20160206.203.ed23711-1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.15+git20160109.147.dd1d655-1",
"0.15+git20160109.147.dd1d655-2",
"0.15+git20160128.179.5def6d9-1",
"0.15+git20160206.203.ed23711-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "golang-github-gohugoio-hugo-dev",
"binary_version": "0.40.1-1"
},
{
"binary_name": "hugo",
"binary_version": "0.40.1-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "hugo",
"purl": "pkg:deb/ubuntu/hugo@0.40.1-1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.25.1-2",
"0.26-1",
"0.35-1",
"0.37.1-1",
"0.38-1",
"0.39-1",
"0.40-1",
"0.40.1-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "hugo",
"binary_version": "0.68.3-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "hugo",
"purl": "pkg:deb/ubuntu/hugo@0.68.3-1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.57.2-1",
"0.58.3-1",
"0.59.1-1.1",
"0.68.3-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "hugo",
"binary_version": "0.92.2-1ubuntu0.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "hugo",
"purl": "pkg:deb/ubuntu/hugo@0.92.2-1ubuntu0.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.80.0-6",
"0.89.4-2",
"0.90.0-1",
"0.90.1-1",
"0.91.0-1",
"0.91.2-1",
"0.92.0-1",
"0.92.1-1build1",
"0.92.2-1",
"0.92.2-1ubuntu0.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "hugo",
"binary_version": "0.123.7-1ubuntu0.3+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:24.04:LTS",
"name": "hugo",
"purl": "pkg:deb/ubuntu/hugo@0.123.7-1ubuntu0.3+esm2?arch=source\u0026distro=esm-apps/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.113.0-3",
"0.119.0-2",
"0.120.3-1",
"0.120.4-1",
"0.121.2-1",
"0.122.0-1",
"0.123.7-1build1",
"0.123.7-1ubuntu0.1",
"0.123.7-1ubuntu0.2",
"0.123.7-1ubuntu0.2+esm1",
"0.123.7-1ubuntu0.3",
"0.123.7-1ubuntu0.3+esm1",
"0.123.7-1ubuntu0.3+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "hugo",
"binary_version": "0.162.1-7"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "hugo",
"purl": "pkg:deb/ubuntu/hugo@0.162.1-7?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.154.5-1",
"0.162.1-5",
"0.162.1-7"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "hugo",
"binary_version": "0.154.5-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "hugo",
"purl": "pkg:deb/ubuntu/hugo@0.154.5-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.131.0-1",
"0.152.2-1",
"0.153.1-3",
"0.153.2-1",
"0.154.2-2",
"0.154.3-1",
"0.154.5-1"
]
}
],
"aliases": [],
"details": "Hugo\u0027s 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.",
"id": "UBUNTU-CVE-2026-10582",
"modified": "2026-10-17T09:37:57Z",
"published": "2026-08-24T11:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-10582"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-10582"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "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",
"type": "CVSS_V4"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-10582"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.