CVE-2026-58403

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

Hugo is a static site generator. From v0.123.0 through v0.163.0, Hugo's virtual filesystem is designed so that files under a mount cannot reach outside the mount tree, but a regression caused RootMappingFs.statRoot to call Stat, which follows symlinks, instead of Lstat, so a direct os.ReadFile "somefile" where somefile was a symlink pointing outside the mount would return the target's contents. This effectively let a symlink planted inside a theme or local mount read arbitrary files reachable to the user running hugo. This issue is fixed in v0.163.1.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
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

Symlink confinement bypass in os.ReadFile · Advisory · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/security/advisories/GHSA-c3wq-j5vh-68rc
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 cf9c8f93ca2a (gohugoio/hugo)

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

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

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

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
hugo0.131.0-1 ... 0.162.1-7 (43 versions)——
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 16× in last 7d / 80× 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 122 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 21:44 UTCEG score recompute
  6. 2026-08-24 21:44 UTCVendor advisory
  7. 2026-08-23 22:25 UTCEG score recompute
  8. 2026-08-23 22:25 UTCVendor advisory
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 23:27 UTCVendor advisory
  11. 2026-08-22 00:24 UTCEG score recompute
  12. 2026-08-22 00:24 UTCVendor advisory
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 01:24 UTCEG score recompute
  15. 2026-08-21 01:24 UTCVendor advisory
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 02:27 UTCEG score recompute
  18. 2026-08-20 02:27 UTCVendor advisory
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-18 22:29 UTCEG score recompute
  21. 2026-08-18 22:29 UTCVendor advisory
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 22:40 UTCEG score recompute
  24. 2026-08-17 22:40 UTCVendor advisory
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 18:27 UTCEG score recompute
  2. 2026-08-16 18:27 UTCVendor advisory
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 19:29 UTCEG score recompute
  6. 2026-08-15 19:29 UTCVendor advisory
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 20:30 UTCEG score recompute
  9. 2026-08-14 20:30 UTCVendor advisory
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 21:28 UTCVendor advisory
  12. 2026-08-12 22:30 UTCEG score recompute
  13. 2026-08-12 22:30 UTCVendor advisory
  14. 2026-08-12 13:51 UTCEPSS rescore
  15. 2026-08-11 23:32 UTCEG score recompute
  16. 2026-08-11 23:32 UTCVendor advisory
  17. 2026-08-11 00:35 UTCEG score recompute
  18. 2026-08-11 00:35 UTCVendor advisory
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 01:37 UTCEG score recompute
  21. 2026-08-10 01:37 UTCVendor advisory
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 02:40 UTCEG score recompute
  24. 2026-08-09 02:40 UTCVendor advisory
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-08 03:42 UTCEG score recompute
  27. 2026-08-08 03:42 UTCVendor advisory
  28. 2026-08-07 04:44 UTCEG score recompute
  29. 2026-08-07 04:44 UTCVendor advisory
  30. 2026-08-06 13:47 UTCEPSS rescore
  31. 2026-08-06 05:46 UTCEG score recompute
  32. 2026-08-06 05:46 UTCVendor advisory
  33. 2026-08-05 19:17 UTCEPSS rescore
  34. 2026-08-05 06:49 UTCEG score recompute
  35. 2026-08-05 06:48 UTCVendor advisory
  36. 2026-08-04 15:10 UTCEPSS rescore
  37. 2026-08-04 10:39 UTCEPSS rescore
  38. 2026-08-04 05:55 UTCVendor advisory
  39. 2026-08-03 06:57 UTCVendor advisory
  40. 2026-08-02 07:59 UTCEG score recompute
  41. 2026-08-02 07:59 UTCVendor advisory
  42. 2026-08-02 02:27 UTCEPSS rescore
  43. 2026-08-01 09:01 UTCEG score recompute
  44. 2026-08-01 09:01 UTCVendor advisory
  45. 2026-08-01 04:16 UTCEPSS rescore
  46. 2026-07-31 10:03 UTCEG score recompute
  47. 2026-07-31 10:03 UTCVendor advisory
  48. 2026-07-30 16:28 UTCEPSS rescore
  49. 2026-07-30 10:51 UTCEG score recompute
  50. 2026-07-30 10:51 UTCVendor advisory
  51. 2026-07-30 01:30 UTCEPSS rescore
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-29 11:49 UTCEG score recompute
  54. 2026-07-28 15:37 UTCEPSS rescore
  55. 2026-07-28 12:51 UTCEG score recompute
  56. 2026-07-27 14:14 UTCEPSS rescore
  57. 2026-07-27 11:45 UTCEG score recompute
  58. 2026-07-26 14:54 UTCEPSS rescore
  59. 2026-07-26 14:54 UTCEPSS rescore
  60. 2026-07-26 12:47 UTCEG score recompute
  61. 2026-07-25 14:18 UTCEPSS rescore
  62. 2026-07-25 14:18 UTCEPSS rescore
  63. 2026-07-24 14:18 UTCEPSS rescore
  64. 2026-07-24 14:18 UTCEPSS rescore
  65. 2026-07-23 14:18 UTCEPSS rescore
  66. 2026-07-23 14:18 UTCEPSS rescore
  67. 2026-07-23 03:21 UTCEG score recompute
  68. 2026-07-22 14:08 UTCEPSS rescore
  69. 2026-07-22 14:08 UTCEPSS rescore
  70. 2026-07-21 15:25 UTCEPSS rescore
  71. 2026-07-21 15:25 UTCEPSS rescore
  72. 2026-07-20 17:08 UTCEPSS rescore
  73. 2026-07-19 14:31 UTCEPSS rescore
  74. 2026-07-19 14:31 UTCEPSS rescore
  75. 2026-07-19 02:29 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-58403?
CVE-2026-58403 is a medium vulnerability published on July 6, 2026. Hugo is a static site generator. From v0.123.0 through v0.163.0, Hugo's virtual filesystem is designed so that files under a mount cannot reach outside the mount tree, but a regression caused RootMappingFs.statRoot to call Stat, which follows symlinks, instead of Lstat, so a direct os.ReadFile…
When was CVE-2026-58403 disclosed?
CVE-2026-58403 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-58403 actively exploited?
CVE-2026-58403 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 60.9% of all scored CVEs.
What is the CVSS score of CVE-2026-58403?
CVE-2026-58403 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-58403?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58403, 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-58403

Explore →

Is Your Infrastructure Affected by CVE-2026-58403?

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

Start Free Scan →Browse All CVEs