CVE-2026-35166 Gohugo CVE debrief

Who should care

Defenders responsible for Hugo installations, particularly those using custom render hooks or trusting Markdown content, should assess exposure and prioritize remediation. This includes operators, platform administrators, vulnerability management teams, and security teams. They should review and update affected deployments, verify and update Hugo installations, and assess potential security issues.

Why it matters

Defenders should prioritize verifying and updating Hugo installations to prevent potential security issues due to improper escaping of links and image links in the default markdown to HTML renderer.

• Potential security issues due to improper escaping of links and image links
• Need to verify and update Hugo installations to prevent exploitation
• Potential impact on deployments using custom render hooks or trusting Markdown content

Technical summary

The Hugo static site generator has a vulnerability in its default markdown to HTML renderer, which does not properly escape links and image links. This vulnerability affects versions from 0.60.0 to before 0.159.2. The vulnerability has a CVSS score of 5.3 and is classified as MEDIUM severity. Defenders should prioritize verifying and updating Hugo installations to prevent potential security issues. The vulnerability can be exploited by attackers to inject malicious code, potentially leading to security issues. Hugo users who trust their Markdown content or have custom render hooks for links and images are not affected.

Defensive priority

Defenders should prioritize verifying and updating Hugo installations to prevent potential security issues.

Recommended defensive actions

• Verify and update Hugo installations to version 0.159.2 or later
• Review and update custom render hooks for links and images
• Assess exposure and prioritize remediation for affected deployments
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, including its description, CVSS score, and affected versions. The vulnerability has a CVSS score of 5.3 and is classified as MEDIUM severity. The affected versions are from 0.60.0 to before 0.159.2. Defenders should verify and update Hugo installations to prevent potential security issues.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.