Hugo: security.http.urls allow-list bypass via HTTP redirects

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2026-50134: 0.40% estimated exploitation activity in the next 30 days; percentile 33.87 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Commit: 86fbb0f7a8 — security: Validate redirects against security.http.urls Affected versions: v0.91.0 (when security.http.urls was introduced) through v0.161.1. Fixed in: v0.162.0. Severity: Only relevant for sites that rely on security.http.urls as a trust boundary — e.g. CI builds that fetch remote resources but want to constrain which hosts can be reached. Not an issue if you fully trust every URL passed to resources.GetRemote. Description. resources.GetRemote enforces security.http.urls on the URL it is called with, but until v0.162.0 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 — for example, http://localhost/ or an internal IP — and Hugo would fetch from the redirected target. The same bypass also lifted any host-shape restriction the operator had put in place. Mitigation. v0.162.0 installs a CheckRedirect on…

Published by the source

16 Jun 2026, 19:22 UTC

Last modified by the source

16 Jun 2026, 19:22 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vxgm-5rmg-5w8g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-50134

Advisory: Hugo: security.http.urls allow-list bypass via HTTP redirects
IDs: CVE-2026-50134, GHSA-vxgm-5rmg-5w8g
Record: https://patchnext.com/advisories/cve-2026-50134 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/gohugoio/hugo 0.162.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/gohugoio/hugo: affected >= 0.91.0, < 0.162.0; fixed in 0.162.0

## Suggested inspection (read-only)
- Go github.com/gohugoio/hugo: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/gohugoio/hugo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vxgm-5rmg-5w8g (GitHub-reviewed advisory GHSA-vxgm-5rmg-5w8g lists affected ranges: Go github.com/gohugoio/hugo >=0.91.0 <0.162.0)

Commands are suggestions: review each one before running it.