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.3%, top 76% 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 — 4 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
23.7%
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

Affected Packages

(1 across 1 ecosystem)
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 18× in last 7d / 18× 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.

  1. 2026-07-12 13:43 UTCEG score recompute
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 14:44 UTCEG score recompute
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-10 15:46 UTCEG score recompute
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 16:48 UTCEG score recompute
  10. 2026-07-08 17:49 UTCEG score recompute▲ 0.60
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 04:32 UTCNVD updateCVSS v3 → 6.5
  14. 2026-07-07 18:50 UTCEG score recompute
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 19:46 UTCEG score recompute
  18. 2026-07-06 19:44 UTCMITRE cvelistV5first tracked

Related CVEs(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 23.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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