Skip to main content
VulnerabilityPublished

CVE-2026-50134: gohugoio hugo · Server-Side Request Forgery (SSRF)

Affects gohugoio hugoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.162.0 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.162.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade hugo and github.com/gohugoio/hugo to 0.162.0.

Affected software

ProductAffectedFixed in
gohugoiohugoAffected
  • >=0.91.0 <0.162.0
Fixed in
  • 0.162.0
Gogithub.com/gohugoio/hugopkg:golang/github.com/gohugoio/hugoOther threatsAffected
  • >=0.91.0 <0.162.0
Fixed in
  • 0.162.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Hugo to version 0.162.0 or later, where this SSRF vulnerability is fixed by proper re-validation of URLs on HTTP redirects. No other mitigation is documented or recommended. Patch status is confirmed fixed in 0.162.0.

Description

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.

References

Community reviews

Loading reviews…