CVE-2026-89258

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

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

Score 6.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-11. A secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-76070 (ENISA EUVD) · GHSA-8jx9-m62j-qx3c (GitHub Security Advisories)Source: ENISA EUVD

6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Hugo is a static site generator. In versions after v0.123.0 and before v0.165.0, symlinks in parent directories were not dropped during direct resource lookups, allowing path confinement to be bypassed. An attacker who can place — or who convinces a site author to place — a symlink inside a mounted directory (for example, in a locally vendored theme under themes/) can cause functions that perform direct lookups, such as resources.Get and os.ReadFile, to follow that symlink and read files outside the intended project boundaries, disclosing their contents in the built site. Themes mounted as Go modules fetched from GitHub have symlinks stripped on download and are not affected, and multi-directory walks (e.g. content/asset walking) are not affected. This issue is an incomplete-fix follow-up to GHSA-c3wq-j5vh-68rc and GHSA-fw87-fv5r-9fpw; it is fixed in v0.165.0.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/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)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
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 (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

September 11, 2026

Last Modified

September 11, 2026

Advisory Details (2)

Auto-updated Sep 11, 2026
Patch available. Sources: github.
Web page

Hugo before v0.165.0 Symlink Confinement Bypass via resources.Get | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hugo-before-0.165.0-symlink-confinement-bypass-via-resources-get
GitHub advisoryMentions a patch (unverified)

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

https://github.com/gohugoio/hugo/security/advisories/GHSA-vrv5-r5rf-6v4j

Vendor Advisories for CVE-2026-89258(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

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.162.1-7 (43 versions)
  • every version up to 0.165.0-1: fixed in 0.165.0-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 53× 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 116 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 16 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-89258?
CVE-2026-89258 is a medium-severity vulnerability; its CVE record was published on September 11, 2026. Hugo is a static site generator. In versions after v0.123.0 and before v0.165.0, symlinks in parent directories were not dropped during direct resource lookups, allowing path confinement to be bypassed. An attacker who can place — or who convinces a site author to place — a symlink inside a mounted…
When was CVE-2026-89258 made public?
CVE-2026-89258 was made public on August 27, 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 September 11, 2026. EchelonGraph's copy of the record carries a last-modified date of September 11, 2026; the record at its source may have been updated since.
Is CVE-2026-89258 actively exploited?
CVE-2026-89258 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89258?
CVE-2026-89258 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89258?
A fix for CVE-2026-89258 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89258 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-89258

Explore →

Is Your Infrastructure Affected by CVE-2026-89258?

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

Book a Demo →Browse All CVEs