CVE-2026-58402

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% 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
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

A fix is available — apply it.

Hugo is a static site generator. From 0.60.0 until 0.163.3, Hugo's default code-block renderer wrote the Markdown code-fence language or info-string into the code class="language-…" data-lang="…" wrapper without HTML escaping. A fence info-string containing a quote and a script payload breaks out of the attribute and injects a live script element. This issue is fixed in 0.163.3.

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

Published

July 6, 2026

Last Modified

July 8, 2026

Advisory Details (4)

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

XSS via unescaped code-fence language in default code block renderer · Advisory · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/security/advisories/GHSA-q76j-gcg9-vxc6
github_release Patch Available

v0.163.3

Patch available: gohugoio/hugo v0.163.3

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

markup/highlight: Escape lang in default code block rendering

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

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

commit ce1a7e0bce37 (gohugoio/hugo)

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

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

Vendor Advisories for CVE-2026-58402(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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
hugo0.100.1-1 ... 0.99.1-1 (146 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
hugo0.111.3-1 ... 0.165.0-3 (83 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
hugo0.131.0-1 ... 0.165.0-3 (46 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
hugo0.131.0-1 ... 0.162.1-7 (43 versions)0.165.0-1—
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/gohugoio/hugo—0.163.3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 57× 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 143 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-58402?
CVE-2026-58402 is a medium vulnerability published on July 6, 2026. Hugo is a static site generator. From 0.60.0 until 0.163.3, Hugo's default code-block renderer wrote the Markdown code-fence language or info-string into the code class="language-…" data-lang="…" wrapper without HTML escaping. A fence info-string containing a quote and a script payload breaks out…
When was CVE-2026-58402 disclosed?
CVE-2026-58402 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-58402 actively exploited?
CVE-2026-58402 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 77.5% of all scored CVEs.
What is the CVSS score of CVE-2026-58402?
CVE-2026-58402 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-58402?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58402, 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-58402

Explore →

Is Your Infrastructure Affected by CVE-2026-58402?

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

Start Free Scan →Browse All CVEs