# CVE-2026-50133: Hugo: XSS via text/html content files

> Attackers can inject malicious scripts via HTML content files in Hugo, leading to stored XSS when sites ingest untrusted HTML.

- **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:** 6 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-50133, GHSA-c54g-xjwj-8g82, GO-2026-5313, JLSEC-2026-794, UBUNTU-CVE-2026-50133

## What is CVE-2026-50133?

CVE-2026-50133 is a medium-severity cross-site scripting vulnerability in gohugoio hugo, published on 6 Jul 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. 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.

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

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

3 open source packages ship an affected version, including github.com/gohugoio/hugo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gohugoio/hugo` | Go | All versions | 0.162.0 |
| `github.com/gohugoio/hugo` | Go | All versions | 0.162.0 |
| `github.com/gohugoio/hugo` | Go | All versions | 0.162.0 |

Products: Gohugo Hugo.

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

Upgrade github.com/gohugoio/hugo to 0.162.0 or later.

## Is CVE-2026-50133 being exploited?

There is no known exploitation of CVE-2026-50133 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-50133 and fix it if it is affected.

What it is: CVE-2026-50133 is a medium-severity cross-site scripting vulnerability in gohugoio hugo, published on 6 Jul 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-50133 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/gohugoio/hugo (Go): affected all versions; fixed in 0.162.0
- github.com/gohugoio/hugo (Go): affected all versions; fixed in 0.162.0
- github.com/gohugoio/hugo (Go): affected all versions; fixed in 0.162.0

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-50133/ (Markdown: https://insights.sbomify.com/CVE-2026-50133/index.md)
```

## Sources

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

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