CVE-2026-10618

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.4 from GitHub Security Advisory published 2026-08-24. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-64776 (ENISA EUVD) · GHSA-2gp4-jcxx-7hpr (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Hugo's default fenced-code-block renderer writes attribute values taken from the code-fence info string into the rendered HTML without escaping them. New in markup/internal/attributes/attributes.go converts every attribute value from a byte slice to a string as it is stored, deliberately dropping the escaping that used to happen there, and RenderAttributes in the same file escapes only values that are still byte slices, so its escaping branch is never reached and every value is written verbatim. The function's documentation states that it performs HTML escaping of string attributes, which it does not. A quote inside an attribute value in the info string therefore terminates the attribute and allows a further attribute, including an event handler, to be placed on the wrapper element, and the script runs for every visitor who loads the page. This path is reached under the default configuration, with code fences enabled and without goldmark's unsafe setting or any custom render hook. Attribute names beginning with on are filtered when the attributes are parsed, so injection is achieved through the value rather than the name.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 24, 2026

Last Modified

October 12, 2026

Advisory Details (5)

Auto-updated Aug 24, 2026
Patch available.
Web page

Hugo 0.93.0 through 0.165.0 Stored Cross-Site Scripting via Unescaped Code-Fence Attribute Values | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hugo-through-stored-cross-site-scripting-via-unescaped-code-fence-attribute-values
Web page

hugo/markup/highlight/highlight.go at v0.165.0 · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/blob/v0.165.0/markup/highlight/highlight.go
Web page

hugo/markup/goldmark/codeblocks/render.go at v0.165.0 · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/blob/v0.165.0/markup/goldmark/codeblocks/render.go
Web page

hugo/markup/internal/attributes/attributes.go at v0.165.0 · gohugoio/hugo · GitHub

https://github.com/gohugoio/hugo/blob/v0.165.0/markup/internal/attributes/attributes.go
Web page

GitHub - gohugoio/hugo: The world’s fastest framework for building websites. · GitHub

https://github.com/gohugoio/hugo

Vendor Advisories for CVE-2026-10618(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.166.0-0.1.hum12026-09-09redhat

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: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.167.0-2 (50 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 77× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 181 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 81 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-10618?
CVE-2026-10618 is a medium-severity vulnerability; its CVE record was published on August 24, 2026. Hugo's default fenced-code-block renderer writes attribute values taken from the code-fence info string into the rendered HTML without escaping them. New in markup/internal/attributes/attributes.go converts every attribute value from a byte slice to a string as it is stored, deliberately dropping…
When was CVE-2026-10618 made public?
CVE-2026-10618 was made public on August 12, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 24, 2026. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-10618 actively exploited?
CVE-2026-10618 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10618?
CVE-2026-10618 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-10618?
A fix for CVE-2026-10618 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-10618 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-10618

Explore →

Is Your Infrastructure Affected by CVE-2026-10618?

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

Book a Demo →Browse All CVEs