CVE-2026-50135

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

Hugo is a static site generator. From 0.123.0 to 0.161.1, a regression made  RootMappingFs.statRoot  use  Stat  (follows symlinks) instead of  Lstat , so a direct  resources.Get  of a symlink pointing outside its mount returned the target's contents — letting a symlink planted in a local mount (e.g. a vendored  themes/  theme) read arbitrary files accessible to the Hugo user. Go-module themes from GitHub (symlinks stripped) and directory walks were unaffected. Fixed in 0.162.0.

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

Published

June 16, 2026

Last Modified

July 8, 2026

Advisory Details (3)

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

v0.162.0

Patch available: gohugoio/hugo v0.162.0

https://github.com/gohugoio/hugo/releases/tag/v0.162.0
github_commit

commit f8b5fa09a649 (gohugoio/hugo)

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

https://github.com/gohugoio/hugo/commit/f8b5fa09a64950c32b803821ede411ebfe772b7a
github Patch Available

Symlink confinement bypass in resources.Get · Advisory · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/security/advisories/GHSA-fw87-fv5r-9fpw

Vendor Advisories for CVE-2026-50135(2)

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.162.1-1.hum12026-06-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.161.1-1 (36 versions)0.162.1-1—
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/gohugoio/hugo—0.162.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 72× 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 106 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-50135?
CVE-2026-50135 is a medium vulnerability published on June 16, 2026. Hugo is a static site generator. From 0.123.0 to 0.161.1, a regression made RootMappingFs.statRoot use Stat (follows symlinks) instead of Lstat , so a direct resources.Get of a symlink pointing outside its mount returned the target's contents — letting a symlink planted in a local mount (e.g. a…
When was CVE-2026-50135 disclosed?
CVE-2026-50135 was first published in the National Vulnerability Database on June 16, 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-50135 actively exploited?
CVE-2026-50135 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 66.0% of all scored CVEs.
What is the CVSS score of CVE-2026-50135?
CVE-2026-50135 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-50135?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50135, 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-50135

Explore →

Is Your Infrastructure Affected by CVE-2026-50135?

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

Start Free Scan →Browse All CVEs