Vulnerability in hugo (UBUNTU-CVE-2026-50135)

Summary

Vulnerability in hugo (UBUNTU-CVE-2026-50135). Confidential information can be exposed externally. Mitigation: upgrade to 0.162.0 or later.

Original description

The description as published by the source.

Hugo is a static site generator. From 0.123.0 to 0.161.1, a regression made RootMappingFs.statRoot use Stat (follows symlinks) instead of Lstat , so a direct resources.Get of a symlink pointing outside its mount returned the target's contents — letting a symlink planted in a local mount (e.g. a vendored themes/ theme) read arbitrary files accessible to the Hugo user. Go-module themes from GitHub (symlinks stripped) and directory walks were unaffected. Fixed in 0.162.0.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-50135 has been found in hugo.
Confidential information can be exposed externally.
What to do: upgrade hugo to 0.162.0 or later.
If unsure, ask your IT team or search "hugo UBUNTU-CVE-2026-50135" on the vendor's site.

UBUNTU-CVE-2026-50135 (hugo)
Attack vector: local / unauthenticated
Patched: 0.162.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in hugo.

📍 Affected scope

Check the vendor advisory for the affected versions of hugo.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 0.162.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'hugo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'hugo' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で hugo を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade hugo to 0.162.0
```
ステージング環境で 0.162.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。