Live › vulnerability › CVE-2026-116117
Go to dashboardHalo, an open-source Java content management system, has a path traversal flaw in its view name resolver, where a crafted template argument can reach files outside the intended directory. A remote attacker who uses the published exploit can read files the server process can access.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 05:28 UTC. All times on this page are UTC.
Any Halo instance at version or earlier that serves requests over a network is in scope, since the flaw is reachable remotely through the template argument. The sources do not say whether authentication is needed or whether a default configuration is affected, so treat all internet-facing Halo deployments as exposed until verified.
2.27.0-beta.1No product ranges from the sources yet.
pom.xml/release used, and compare it with 2.27.0-beta.12.27.0-beta.1Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A flaw has been found in halo-dev halo up to 2.27.0-beta.1. Affected by this vulnerability is the function run.halo.app.theme.DefaultViewNameResolver.resolveViewNameOrDefault of the file application/src/main/java/run/halo/app/theme/DefaultViewNameResolver.java of the component View Name Resolver. Executing a manipulation of the argument template can lead to path traversal. The attack may be launched remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
This page as .md · .json · in your agent: get_signal("CVE-2026-116117")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.