CVE-2026-50134 hugo vulnerability
Hugo is a static site generator. From 0.91.0 until 0.162.0, resources.GetRemote enforces security.http.urls on the URL it is called with, but it did not re-validate intermediate URLs on HTTP 3xx redirects. An allowed server (or an attacker controlling its DNS or response) could therefore redirect the request to a host that the policy was meant to forbid and Hugo would fetch from the redirected target. The same bypass also lifted any host-shape restriction the operator had put in place. This vulnerability is fixed in 0.162.0.
Quick answer
gohugo hugo should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
Hugo is affected by CVE-2026-50134, a SSRF and internal request risk. Hugo is a static site generator. The recommended remediation is to update to Hugo 0.162.0 or later. Until the update is complete, avoid untrusted resources.GetRemote URLs and enforce redirect destination validation for internal or metadata hosts, review logs, and reduce exposure of the affected service, firmware path, or build workflow.
- Inventory every deployment, package, firmware image, appliance, device family, container, build runner, or service that uses Hugo.
- Confirm the installed version or firmware build and compare it with versions from 0.91.0 through 0.162.0 and the source advisory for CVE-2026-50134.
- Apply the vendor-supported fix: update to Hugo 0.162.0 or later.
- If the update cannot be applied immediately, avoid untrusted resources.GetRemote URLs and enforce redirect destination validation for internal or metadata hosts; disable unnecessary public access, endpoints, uploads, build inputs, hardware features, or high-risk integrations until patched.
- Review application, device, kernel, firmware, build, package manager, container, authentication, and audit logs for activity related to CVE-2026-50134.
- Rotate sessions, API tokens, service credentials, signing keys, integration keys, and administrator passwords if logs or affected data indicate compromise, code execution, credential exposure, or unauthorized access.
- Clear caches, restart affected services, rebuild affected containers or firmware images when appropriate, and remove temporary files, generated artifacts, stored payloads, or unsafe configuration created during exploitation attempts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Hugo now reports Hugo 0.162.0 or later or a later vendor-supported fixed release/build for the deployed branch or device family.
- Verify the affected workflow no longer allows the behavior described in CVE-2026-50134, using a safe regression test, vendor validation method, or firmware/package inventory check.
- Review logs after remediation for continued exploit attempts, denial-of-service symptoms, suspicious redirects, unauthorized requests, file access, memory corruption symptoms, or configuration changes.
- Rerun a Fixnx scan and any product-specific scanner, package audit, firmware inventory, device health check, or manual regression test relevant to the affected service.
- Document affected assets, fixed versions, mitigation decisions, validation evidence, and any cleanup, rebuild, or credential rotation performed.
Trusted references
FAQ
What is affected by CVE-2026-50134?
gohugo hugo should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.