# CVE-2026-100694: Hugo before 0.166.0 Cross-Site Scripting via text/org

> Attackers can inject scripts into Hugo-generated sites via unescaped Org Mode content, affecting visitors' browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-100694, GHSA-98xc-jpvp-56pj, GHSA-pq74-mj4h-cjq2, MINI-ch86-gfj3-2xxh, MINI-w4p4-4725-c49r, UBUNTU-CVE-2026-100694

## What is CVE-2026-100694?

CVE-2026-100694 is a medium-severity cross-site scripting vulnerability in gohugoio hugo, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Hugo is a static site generator. In versions from v0.56.0 through v0.165.x, content files mapped to the text/org media type are rendered without escaping raw HTML: Org export blocks and @@html:...@@ snippets pass HTML through unescaped, resulting in cross-site scripting (XSS) in the generated site. An attacker who can supply or influence a content file under /content or the output of a content adapter can inject scripts that execute in the browsers of visitors to the affected pages. Only pages whose source file or content-adapter output declares the text/org media type are affected, and sites that fully trust all content sources are not impacted. Version v0.166.0 fixes the issue by introducing a security.allowContent allowlist that denies text/org by default; sites that intentionally author Org Mode content can opt back in with [security] allowContent = ['.*'].

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Gohugo Hugo.

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

Upgrade to a fixed version.

## Is CVE-2026-100694 being exploited?

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

## Other vulnerabilities in gohugoio hugo

- [CVE-2026-75926](https://insights.sbomify.com/CVE-2026-75926/): Hugo 0.162.0 to 0.164.x - Node Permission Model Bypass via Default TailwindCSS Child-Process Grant (critical 9.3)
- [CVE-2026-100690](https://insights.sbomify.com/CVE-2026-100690/): Hugo v0.161.0 to v0.165.0 Arbitrary File Read via Symlinks (high 8.7)
- [CVE-2026-100692](https://insights.sbomify.com/CVE-2026-100692/): Hugo before v0.166.0 Path Traversal via Symlinked Mount Roots (high 8.7)
- [CVE-2026-100693](https://insights.sbomify.com/CVE-2026-100693/): Hugo v0.162.0 before v0.166.0 IP-literal Deny Rule Bypass (high 8.6)
- [CVE-2020-26284](https://insights.sbomify.com/CVE-2020-26284/): Hugo can execute a binary from the current directory on Windows (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100694 is a medium-severity cross-site scripting vulnerability in gohugoio hugo, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-100694 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-100694/ (Markdown: https://insights.sbomify.com/CVE-2026-100694/index.md)
```

## Sources

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

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