CVE-2026-50133

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

Hugo is a static site generator. Prior to 0.162.0, Hugo accepts content files in several markup formats. Files mapped to the text/html media type (typically .html files under /content, or pages produced by a content adapter that sets content.mediaType = "text/html") had their body emitted verbatim into the rendered page. A site that ingests HTML content from an untrusted source could therefore be served stored cross-site scripting. This vulnerability is fixed in 0.162.0.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

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
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

Published

June 16, 2026

Last Modified

July 8, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
Patch available. Sources: github_release, github, github_commit.
githubMentions a patch (unverified)

XSS via text/html content files · Advisory · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/security/advisories/GHSA-c54g-xjwj-8g82
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 e41a06447daa (gohugoio/hugo)

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

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

Vendor Advisories for CVE-2026-50133(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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
hugo0.100.1-1 ... 0.99.1-1 (146 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
hugo0.111.3-1 ... 0.167.0-2 (87 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
hugo0.131.0-1 ... 0.167.0-2 (50 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
hugo0.131.0-1 ... 0.161.1-1 (36 versions)
  • every version up to 0.162.1-1: fixed in 0.162.1-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/gohugoio/hugo—
  • every version up to 0.162.0: fixed in 0.162.0
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-50133?
CVE-2026-50133 is a medium vulnerability published on June 16, 2026. Hugo is a static site generator. Prior to 0.162.0, Hugo accepts content files in several markup formats. Files mapped to the text/html media type (typically .html files under /content, or pages produced by a content adapter that sets content.mediaType = "text/html") had their body emitted verbatim…
When was CVE-2026-50133 disclosed?
CVE-2026-50133 was first published 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-50133 actively exploited?
CVE-2026-50133 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50133?
CVE-2026-50133 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-50133?
A fix for CVE-2026-50133 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50133 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50133

Explore →

Is Your Infrastructure Affected by CVE-2026-50133?

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

Book a Demo →Browse All CVEs