Live › vulnerability › CVE-2026-84823
Go to dashboardA user with the lowest standard WildFly RBAC role, Monitor, can use a path traversal in the take-snapshot operation's name parameter to write a copy of the server configuration to an arbitrary location. That lets the Monitor user read back the configuration, including credentials that RBAC would otherwise hide.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
WildFly (org.wildfly.core) servers with RBAC enabled and at least one account mapped to the Monitor role who is not trusted with the server configuration. The flaw lets that account use take-snapshot to write the config, with credentials, to a location it can read. Servers whose management interface is reachable only by admins, or that run without RBAC, can skip it. Affected versions are not published yet.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| org.wildfly.core | maven | unknown | – |
rbac, accounts with the Monitor role can reach the flaw; if simple, no Monitor role is enforcedEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A flaw was found in WildFly. A user with the Monitor role, which is the lowest standard Role-Based Access Control (RBAC) role, can exploit a path traversal vulnerability in the take-snapshot operation. By manipulating the name parameter, this user can write a copy of the server configuration to an arbitrary location. This allows the Monitor role to read back the server configuration, including sensitive credentials, which would otherwise be restricted by RBAC, leading to information disclosure.
This page as .md · .json · in your agent: get_signal("CVE-2026-84823")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.