CVE-2026-10582

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. a secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
7.4
EG Score
7.4(high)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 24, 2026

Advisory Details (4)

Auto-updated Aug 24, 2026
No patch confirmed yet. Sources: github.
generic

Hugo 0.91.0 through 0.165.0 Server-Side Request Forgery via security.http.urls Lacking Destination Address Validation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hugo-through-server-side-request-forgery-via-security-http-urls-lacking-destination-address-validation
generic

hugo/resources/resource_factories/create/create.go at v0.165.0 · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/blob/v0.165.0/resources/resource_factories/create/create.go
github

hugo/config/security/securityConfig.go at v0.165.0 · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/blob/v0.165.0/config/security/securityConfig.go
generic

GitHub - gohugoio/hugo: The world’s fastest framework for building websites. · GitHub

https://github.com/gohugoio/hugo

Vendor Advisories for CVE-2026-10582(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhathugo-main-0.166.0-0.1.hum12026-09-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
hugo0.111.3-1 ... 0.165.0-2 (82 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
hugo0.131.0-1 ... 0.165.0-2 (45 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
hugo0.131.0-1 ... 0.165.0-2 (45 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 32× in last 7d / 117× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 117 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-20 15:25 UTCVendor advisory
  3. 2026-09-20 15:25 UTCGHSA enrichment
  4. 2026-09-20 02:19 UTCEG score recompute
  5. 2026-09-20 02:19 UTCVendor advisory
  6. 2026-09-20 02:19 UTCGHSA enrichment
  7. 2026-09-19 13:12 UTCVendor advisory
  8. 2026-09-19 13:12 UTCGHSA enrichment
  9. 2026-09-19 00:06 UTCEG score recompute
  10. 2026-09-19 00:06 UTCVendor advisory
  11. 2026-09-19 00:05 UTCGHSA enrichment
  12. 2026-09-18 19:27 UTCEPSS rescore
  13. 2026-09-18 10:59 UTCVendor advisory
  14. 2026-09-18 10:59 UTCGHSA enrichment
  15. 2026-09-17 21:52 UTCEG score recompute
  16. 2026-09-17 21:52 UTCVendor advisory
  17. 2026-09-17 21:52 UTCGHSA enrichment
  18. 2026-09-17 08:46 UTCVendor advisory
  19. 2026-09-17 08:46 UTCGHSA enrichment
  20. 2026-09-16 19:39 UTCEG score recompute
  21. 2026-09-16 19:39 UTCVendor advisory
  22. 2026-09-16 19:39 UTCGHSA enrichment
  23. 2026-09-16 05:14 UTCEPSS rescore
  24. 2026-09-16 04:37 UTCVendor advisory
  25. 2026-09-16 04:37 UTCGHSA enrichment
Show 75 more
  1. 2026-09-15 15:11 UTCEG score recompute
  2. 2026-09-15 15:11 UTCVendor advisory
  3. 2026-09-15 15:11 UTCGHSA enrichment
  4. 2026-09-15 01:54 UTCVendor advisory
  5. 2026-09-15 01:54 UTCGHSA enrichment
  6. 2026-09-14 12:47 UTCVendor advisory
  7. 2026-09-14 12:47 UTCGHSA enrichment
  8. 2026-09-13 23:40 UTCEG score recompute
  9. 2026-09-13 23:40 UTCVendor advisory
  10. 2026-09-13 23:40 UTCGHSA enrichment
  11. 2026-09-13 16:46 UTCEPSS rescore
  12. 2026-09-13 10:34 UTCVendor advisory
  13. 2026-09-13 10:34 UTCGHSA enrichment
  14. 2026-09-12 21:25 UTCEG score recompute
  15. 2026-09-12 21:25 UTCVendor advisory
  16. 2026-09-12 21:25 UTCGHSA enrichment
  17. 2026-09-12 15:00 UTCEPSS rescore
  18. 2026-09-12 08:19 UTCVendor advisory
  19. 2026-09-12 08:19 UTCGHSA enrichment
  20. 2026-09-11 19:12 UTCEG score recompute
  21. 2026-09-11 19:12 UTCVendor advisory
  22. 2026-09-11 19:12 UTCGHSA enrichment
  23. 2026-09-11 14:52 UTCEPSS rescore
  24. 2026-09-11 09:36 UTCEPSS rescore
  25. 2026-09-11 06:01 UTCVendor advisory
  26. 2026-09-11 06:01 UTCGHSA enrichment
  27. 2026-09-10 16:54 UTCEG score recompute
  28. 2026-09-10 16:54 UTCVendor advisory
  29. 2026-09-10 16:54 UTCGHSA enrichment
  30. 2026-09-10 09:34 UTCEPSS rescore
  31. 2026-09-10 03:47 UTCGHSA enrichment
  32. 2026-09-09 14:40 UTCGHSA enrichment
  33. 2026-09-09 01:34 UTCEG score recompute
  34. 2026-09-09 01:34 UTCGHSA enrichment
  35. 2026-09-08 22:00 UTCEPSS rescore
  36. 2026-09-08 04:29 UTCEG score recompute
  37. 2026-09-08 04:29 UTCGHSA enrichment
  38. 2026-09-07 16:01 UTCEPSS rescore
  39. 2026-09-07 15:22 UTCGHSA enrichment
  40. 2026-09-07 01:34 UTCEG score recompute
  41. 2026-09-07 01:33 UTCGHSA enrichment
  42. 2026-09-06 13:47 UTCEPSS rescore
  43. 2026-09-06 12:24 UTCGHSA enrichment
  44. 2026-09-05 23:18 UTCEG score recompute
  45. 2026-09-05 23:18 UTCGHSA enrichment
  46. 2026-09-05 10:11 UTCGHSA enrichment
  47. 2026-09-04 21:04 UTCEG score recompute
  48. 2026-09-04 21:04 UTCGHSA enrichment
  49. 2026-09-04 07:10 UTCEG score recompute
  50. 2026-09-04 07:10 UTCGHSA enrichment
  51. 2026-09-04 05:06 UTCEPSS rescore
  52. 2026-09-03 17:31 UTCGHSA enrichment
  53. 2026-09-03 04:22 UTCGHSA enrichment
  54. 2026-09-02 15:10 UTCEG score recompute
  55. 2026-09-02 15:10 UTCGHSA enrichment
  56. 2026-09-02 14:11 UTCEPSS rescore
  57. 2026-09-02 01:47 UTCEG score recompute
  58. 2026-09-02 01:47 UTCGHSA enrichment
  59. 2026-09-01 13:53 UTCEPSS rescore
  60. 2026-09-01 12:40 UTCEG score recompute
  61. 2026-09-01 12:40 UTCGHSA enrichment
  62. 2026-09-01 04:39 UTCEPSS rescore
  63. 2026-08-31 23:19 UTCGHSA enrichment
  64. 2026-08-31 10:12 UTCGHSA enrichment
  65. 2026-08-30 21:00 UTCEG score recompute
  66. 2026-08-30 21:00 UTCGHSA enrichment
  67. 2026-08-30 19:17 UTCEPSS rescore
  68. 2026-08-30 07:54 UTCEG score recompute
  69. 2026-08-30 07:54 UTCGHSA enrichment
  70. 2026-08-30 01:21 UTCEPSS rescore
  71. 2026-08-29 18:45 UTCGHSA enrichment
  72. 2026-08-29 05:36 UTCEG score recompute
  73. 2026-08-29 05:36 UTCGHSA enrichment
  74. 2026-08-28 21:40 UTCEPSS rescore
  75. 2026-08-28 16:27 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Same vendor

1 shown

redhat:RHSA-2026:66266

Frequently asked(5)

What is CVE-2026-10582?
CVE-2026-10582 is a high vulnerability published on August 24, 2026. 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…
When was CVE-2026-10582 disclosed?
CVE-2026-10582 was first published in the National Vulnerability Database on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10582 actively exploited?
CVE-2026-10582 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.4% of all scored CVEs.
What is the CVSS score of CVE-2026-10582?
CVE-2026-10582 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-10582?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10582, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10582

Explore →

Is Your Infrastructure Affected by CVE-2026-10582?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs