Quick answers
- Is CVE-2026-17614 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17614 being exploited in the wild.
- How severe is CVE-2026-17614?
- Medium severity, with a CVSS score of 4.4, published 4 August 2026.
- Which products and versions are affected?
- Red Hat WildFly <UNKNOWN>.
- Is there a fix for CVE-2026-17614?
- 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-17614 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-17614?
- Check whether you run Red Hat WildFly 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
The vulnerability exists in the LocalFileRepository.getFile() and getConfigurationFile() methods in wildfly-core/deployment-repository, which fail to validate that resolved file paths remain within configured repository or configuration directories. A remote attacker with the slave host controller secret or who has 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. The Domain Controller will then resolve and serve arbitrary files readable by the DC process. No patch availability information is provided in the advisory.
Affected products
- Red Hat WildFly <UNKNOWN>
Timeline
- 2026-08-04: disclosed