Skip to content
VulniPulse
Medium4.4Red Hat Linux

Medium [CVE-2026-17614] Wildfly-core: path traversal on wildfly domain controller

This medium-severity Red Hat Linux advisory covers CVE-2026-17614 affecting Red Hat JBoss Enterprise Application Platform 7, Red Hat JBoss Enterprise Application Platform 8, Red Hat JBoss Enterprise Application Platform Expansion Pack.

CVE-2026-17614 Published Aug 4, 2026Updated by vendor Aug 4, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A path traversal flaw was found in WildFly's domain mode implementation.

The LocalFileRepository.getFile() 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.

Affected products named by the advisory: Red Hat JBoss Enterprise Application Platform 7; Red Hat JBoss Enterprise Application Platform 8; Red Hat JBoss Enterprise Application Platform Expansion Pack; Red Hat Single Sign-On 7.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · medium-confidence parse· fetched 2 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.