VulnerabilityPublished 4 Aug 2026Updated 6 Nov 2026

CVE-2026-17614: WildFly's domain mode implementation · Path Traversal Flaw Was Found

Source GCVE Database

Compare

Authoritative record:CVE-2026-17614· Medium 4.4

Not known to be exploited · CVSS 4.4 Medium : update Red Hat JBoss Enterprise Application Platform 7 when convenient.

Data as of 6 Nov 2026, 19:33 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	4.4

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-62xj-w627-m337

What to do

Patches and advisories

access.redhat.com/errata/RHSA-2026:95887 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Red Hat JBoss Enterprise Application Platform 8.1wildfly-deployment-repository	Affected–	Fixed in–
Red Hat JBoss Enterprise Application Platform 7eap74-els-openjdk11-openshift-rhel8/eap74-els-openjdk11-openshift-rhel8	Affected–	Fixed in–
Red Hat JBoss Enterprise Application Platform 7eap74-els-openjdk17-openshift-rhel8/eap74-els-openjdk17-openshift-rhel8	Affected–	Fixed in–
Red Hat JBoss Enterprise Application Platform 7eap74-els-openjdk8-openshift-rhel8/eap74-els-openjdk8-openshift-rhel8	Affected–	Fixed in–
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7-eap74-els-openjdk17-openshift-rhel8/jboss-eap-7-eap74-els-openjdk17-openshift-rhel8	Affected–	Fixed in–
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7-eap74-els-openjdk8-openshift-rhel8/jboss-eap-7-eap74-els-openjdk8-openshift-rhel8	Affected–	Fixed in–

AI-suggested

A security update is available in Red Hat JBoss Enterprise Application Platform 8.1.9, which includes fixes for this vulnerability. Users should apply this official patch to remediate the issue. Since the vulnerability requires access to the slave host controller secret or a compromised slave host controller, protecting these credentials and limiting access to trusted entities also helps mitigate risk. No additional vendor advisory states that no action is required or that the issue is already mitigated.

Description

A path traversal vulnerability exists in WildFly's domain mode implementation, specifically in the LocalFileRepository.getFile() and getConfigurationFile() methods. These methods fail to validate that resolved file paths remain within the configured repository or configuration root directories. An attacker with access to a compromised slave host controller or its secret can exploit this flaw by supplying crafted relative paths via the slave-DC wire protocol, causing the Domain Controller to disclose arbitrary files accessible to its process, including sensitive configuration files and credentials.

Impact

The vulnerability allows unauthorized disclosure of sensitive information from the Domain Controller process by exploiting path traversal to access arbitrary files. This includes configuration files, keystores, and system credentials, potentially aiding further attacks or system compromise. Exploitation requires prior compromise or knowledge of the slave host controller secret, limiting the attack surface to privileged or already compromised entities.

CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path Traversal) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Patches and advisories

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 19:33 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats