Quick answers
- Is CVE-2026-116117 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116117 being exploited in the wild.
- How severe is CVE-2026-116117?
- High severity, with a CVSS score of 7.3, published 26 October 2026.
- Which products and versions are affected?
- Halo-Dev Halo up to 2.27.0-beta.1.
- Is there a fix for CVE-2026-116117?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-116117 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116117?
- Check whether you run Halo-Dev Halo 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.
Technical details
A path traversal vulnerability exists in the DefaultViewNameResolver.resolveViewNameOrDefault function in Halo's View Name Resolver component. The flaw allows remote attackers to manipulate the template argument without authentication to escape directory restrictions. An exploit has been publicly disclosed.
Affected products
- halo-dev Halo up to 2.27.0-beta.1
Timeline
- 2026-10-26: disclosed
- other: Exploit published publicly