CVE-2026-85634
Wildfly-core: wildfly-core: deployer rbac role privilege escalation via path traversal in deployment name
What happened?
A flaw was found in the ContentRepositoryImpl.copyExplodedContent function of the wildfly-core library, which is used by WildFly and JBoss EAP to manage server deployments. The issue occurs when the library processes an unsanitized deployment name. Due to a missing containment check, an attacker with the Deployer RBAC role can use path traversal sequences to access files outside the restricted deployment directory. This can allow the attacker to delete arbitrary directories or create files with arbitrary content, leading to a full privilege escalation to the management SuperUser role.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| wildfly-serverRed Hat | Default status: unaffected | See vendor advisory |
| wildfly-serverRed Hat | Default status: unaffected | See vendor advisory |
| jboss-eap-7/eap74-els-openjdk11-openshift-rhel8Red Hat | Default status: affected | See vendor advisory |
| jboss-eap-7/eap74-els-openjdk17-openshift-rhel8Red Hat | Default status: affected | See vendor advisory |
| jboss-eap-7/eap74-els-openjdk8-openshift-rhel8Red Hat | Default status: affected | See vendor advisory |
| wildfly-serverRed Hat | Default status: affected | See vendor advisory |
| wildfly-serverRed Hat | Default status: unaffected | See vendor advisory |
| wildfly-serverRed Hat | Default status: affected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.