Quick answers
- Is CVE-2026-109595 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109595 being exploited in the wild.
- How severe is CVE-2026-109595?
- Medium severity, with a CVSS score of 5.5, published 12 October 2026.
- Which products and versions are affected?
- Hugo v0.84.0 through v0.166.x.
- Is there a fix for CVE-2026-109595?
- Yes: fixed in v0.167.0. Until then: Do not use themes or modules you do not trust. Review imports in js.Build, js.Batch, and css.Build entry points for paths that leave the project. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109595 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-109595?
- Check whether you run Hugo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: v0.167.0
Do not use themes or modules you do not trust. Review imports in js.Build, js.Batch, and css.Build entry points for paths that leave the project.
Technical details
The vulnerability exists in Hugo's js.Build, js.Batch, and css.Build functions, which delegate to ESBuild's resolver for imports not found in /assets. ESBuild reads directly from the filesystem without Hugo's security restrictions and follows symlinks, allowing a malicious theme to traverse outside the project root. An attacker ships a theme with relative imports (e.g., import secret from "../secret.txt") or symlinks pointing outside the project, which get bundled into published output readable by the build user.
Affected products
- Hugo Hugo v0.84.0 through v0.166.x
Timeline
- 2026-09-28: disclosed
- 2026-09-28: patched: Fixed in v0.167.0