# CVE-2026-89258: Hugo before v0.165.0 Symlink Confinement Bypass via resources.Get

> An attacker can bypass path confinement via symlinks in mounted directories to read files outside the project boundaries, disclosing sensitive content.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-89258, GHSA-8jx9-m62j-qx3c, GHSA-vrv5-r5rf-6v4j, MINI-pvjf-vqm3-fmw4, MINI-v339-m5f7-pxrp, UBUNTU-CVE-2026-89258

## What is CVE-2026-89258?

CVE-2026-89258 is a critical path traversal vulnerability in gohugoio hugo, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-89258?


## How do I fix CVE-2026-89258?

Upgrade to a fixed version.

## Is CVE-2026-89258 being exploited?

There is no known exploitation of CVE-2026-89258 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89258 and fix it if it is affected.

What it is: CVE-2026-89258 is a critical path traversal vulnerability in gohugoio hugo, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89258 in the wild and no public exploit code.

Affected product: gohugoio hugo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89258/ (Markdown: https://insights.sbomify.com/CVE-2026-89258/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89258
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89258
- OSV: https://osv.dev/vulnerability/CVE-2026-89258

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89258/
Summaries are generated and may contain mistakes; the official description above is the record.