Skip to content
Noroxi
CVE-2026-35166· NVD / CVE Program· CNA GitHub_M

Hugo does not properly escape some Markdown links

Hugo is a static site generator. From 0.60.0 to before 0.159.2, links and image links in the default markdown to HTML renderer are not properly escaped. Hugo users who trust their Markdown content or have custom render hooks for links and images are not affected. This vulnerability is fixed in 0.159.2.

MediumCVSS 5.3 · v4.0—No exploit Fix available
Published
Apr 6, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 13th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
5.3
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
gohugohugo

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gohugo hugo0.60.0 and later · before 0.159.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • gohugoio hugo

    • >= 0.60.0, < 0.159.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12hugoall versions—
Debian:14hugobefore 0.159.2-10.159.2-1
Gogithub.com/gohugoio/hugofrom 0.60.0 · before 0.159.20.159.2
Red Hat:hummingbird:1hugobefore 0:0.160.1-2.hum10:0.160.1-2.hum1

Other highest-scoring records for the same primary product.

  • CVE-2026-75926Hugo 0.162.0 to 0.164.x - Node Permission Model Bypass via Default TailwindCSS Child-Process Grant
    37Monitor
  • CVE-2026-100693Hugo v0.162.0 before v0.166.0 IP-literal Deny Rule Bypass
    34Monitor
  • CVE-2026-100692Hugo before v0.166.0 Path Traversal via Symlinked Mount Roots
    34Monitor
  • CVE-2026-100690Hugo v0.161.0 to v0.165.0 Arbitrary File Read via Symlinks
    34Monitor
  • CVE-2020-26284Hugo can execute a binary from the current directory on Windows
    34Monitor
  • CVE-2026-50135Hugo: Symlink confinement bypass in resources.Get
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
gohugoio hugo0.159.2 · descriptionVendor (CNA)
debian:hugo0.159.2-1 · Debian:14Package registry (OSV)
Go:github.com/gohugoio/hugo0.159.2Package registry (OSV)
red hat:hugo0:0.160.1-2.hum1 · Red Hat:hummingbird:1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-5013391 days apartHugo: XSS via text/html content files
    20Monitor
  • CVE-2026-5840291 days apartHugo default code block renderer XSS via unescaped code-fence language
    20Monitor
  • CVE-2026-100691173 days apartHugo before 0.166.0 Stored XSS via lineAnchors code block option
    20Monitor
  • CVE-2026-100694173 days apartHugo before 0.166.0 Cross-Site Scripting via text/org
    20Monitor
  • CVE-2026-10618140 days apartHugo 0.93.0 through 0.165.0 Stored Cross-Site Scripting via Unescaped Code-Fence Attribute Values
    19Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
P
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
commentEl.innerHTML = comment.body;

Fixed

ts
commentEl.textContent = comment.body;

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records