CVE-2026-58404

MEDIUMNVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

A fix is available — apply it.

Hugo is a static site generator. From v0.162.0 through v0.163.0, the default security.http.urls policy denies requests to loopback, internal, and cloud-metadata IPv4 literals, but the deny rule only matched dotted-decimal notation, so alternate IPv4 encodings of the same addresses, including integer, hex, or octal, passed the policy. When a template passes an untrusted or data-derived URL to resources.GetRemote and the host platform uses the cgo system resolver, these encodings resolve to the blocked address, allowing build-time server-side requests to loopback and internal services, including the cloud-metadata endpoint in hosted or CI builds; the same check is reused on redirects, so the gap also applies to each redirect hop. This issue is fixed in v0.163.1.

CVSS v3
6.8
EG Score
6.8(medium)
EG Risk
31(Track)
EG Risk 31/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
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 8, 2026

Advisory Details (4)

Auto-updated Jul 7, 2026
Patch available. Sources: github_pr, github_release, github, github_commit.
github Patch Available

security.http.urls deny rules bypassed by alternate IPv4 encodings (SSRF) · Advisory · gohugoio/hugo · GitHub

Affected: v0.163.1).

https://github.com/gohugoio/hugo/security/advisories/GHSA-r46f-3rpw-hxrv
github_release Patch Available

v0.163.1

Patch available: gohugoio/hugo v0.163.1

https://github.com/gohugoio/hugo/releases/tag/v0.163.1
github_pr

Misc adjustments

Fix merged in gohugoio/hugo PR #15020 on 2026-06-10 — awaiting tagged release

https://github.com/gohugoio/hugo/pull/15020
github_commit

commit a00b5c72ac57 (gohugoio/hugo)

Fix landed in gohugoio/hugo commit a00b5c72ac57 — awaiting tagged release

https://github.com/gohugoio/hugo/commit/a00b5c72ac57afe26df6688ece3ca544a56df372

Vendor Advisories for CVE-2026-58404(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.163.3-0.1.hum12026-07-08redhat

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

(2 across 2 ecosystems)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
hugo0.131.0-1 ... 0.162.1-7 (43 versions)——
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/gohugoio/hugo—0.163.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 76× 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 116 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-58404?
CVE-2026-58404 is a medium vulnerability published on July 6, 2026. Hugo is a static site generator. From v0.162.0 through v0.163.0, the default security.http.urls policy denies requests to loopback, internal, and cloud-metadata IPv4 literals, but the deny rule only matched dotted-decimal notation, so alternate IPv4 encodings of the same addresses, including…
When was CVE-2026-58404 disclosed?
CVE-2026-58404 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58404 actively exploited?
CVE-2026-58404 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 70.4% of all scored CVEs.
What is the CVSS score of CVE-2026-58404?
CVE-2026-58404 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-58404?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58404, 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-58404

Explore →

Is Your Infrastructure Affected by CVE-2026-58404?

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

Start Free Scan →Browse All CVEs