CVE-2026-17614 in WildFly
Summary
by MITRE • 08/04/2026
A path traversal flaw was found in WildFly's domain mode implementation. The LocalFileRepository.getFile() and getConfigurationFile() methods in wildfly-core/deployment-repository do not validate that the resolved file path remains within the configured repository or configuration root directories. A remote attacker who has obtained the slave host controller secret or compromised a slave host controller can supply a crafted relative path containing directory traversal sequences (e.g., ../../etc/passwd) via the slave-DC wire protocol, causing the Domain Controller to resolve and serve arbitrary files readable by the DC process. This leads to unauthorized disclosure of sensitive information such as configuration files, keystores, and system credentials.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 08/04/2026
This vulnerability represents a critical path traversal flaw within WildFly's domain mode implementation that exploits the insufficient validation mechanisms in the LocalFileRepository component. The issue resides in the wildfly-core/deployment-repository module where the getFile() and getConfigurationFile() methods fail to properly constrain file path resolution operations, allowing malicious actors to bypass intended directory boundaries through crafted relative paths containing directory traversal sequences.
The technical exploitation occurs through the slave-DC wire protocol, which enables communication between domain controllers and slave host controllers in WildFly's distributed architecture. Attackers who have either obtained the slave host controller secret through credential compromise or successfully compromised a slave host controller can manipulate file path resolution by injecting traversal sequences such as ../../etc/passwd into their requests. This flaw directly violates security principles around input validation and path containment, creating an unauthorized access vector that operates at the core of WildFly's domain management infrastructure.
The operational impact of this vulnerability extends beyond simple information disclosure to encompass potential system compromise through access to sensitive configuration files, keystores, and system credentials. Domain controllers running with elevated privileges can be coerced into serving arbitrary files that would normally be restricted to authorized users, effectively breaking the security boundaries established by WildFly's domain mode architecture. This represents a significant threat to enterprise environments where WildFly serves as a core application server platform for mission-critical applications.
Organizations utilizing WildFly in domain mode should immediately implement mitigations including restricting network access to slave-DC wire protocol endpoints, enforcing strict authentication and authorization controls for host controller communications, and applying the vendor-provided security patches that address this path traversal vulnerability. The flaw aligns with CWE-22 Path Traversal vulnerabilities and maps to attack techniques within the MITRE ATT&CK framework related to privilege escalation and credential access through insecure file handling mechanisms. Security monitoring should focus on unusual file access patterns and unauthorized attempts to retrieve system configuration data from domain controller endpoints.
This vulnerability highlights the importance of proper input validation in distributed application server architectures where multiple components must maintain secure communication boundaries while providing necessary functionality. The implementation deficiency demonstrates how seemingly simple path resolution operations can become critical security weaknesses when proper boundary checking mechanisms are omitted, emphasizing the need for comprehensive security testing of inter-component communication protocols in enterprise software platforms.