Org.wildfly.core:wildfly-server: wildfly improper rbac permission (CVE-2025-23367)

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps org.wildfly.core:wildfly-server (maven), org.wildfly.core:wildfly-server (maven). Check affected ranges and fixed versions before updating.

Affected products and reported versions
Product	Affected versions	Fixed versions
cpe:2.3:a:redhat:jboss_enterprise_application_platform::::::::	Not reported	Not reported
cpe:2.3:a:redhat:wildfly::::::::	Not reported	Not reported
cpe:2.3:a:redhat:wildfly:28.0.0:beta1::::::	Not reported	Not reported

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
org.wildfly.core:wildfly-servermaven	>=0 <27.0.1.Final	27.0.1.Final
org.wildfly.core:wildfly-servermaven	>=28.0.0.Beta1 <28.0.0.Beta2	28.0.0.Beta2

Recommended response

Check inventory. Check lockfiles and deployed manifests for org.wildfly.core:wildfly-server, org.wildfly.core:wildfly-server.
Review the reported fix. Update org.wildfly.core:wildfly-server to 27.0.1.Final; org.wildfly.core:wildfly-server to 28.0.0.Beta2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Jan 30, 2025
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 4, 2026

Sources and claim methodology

Upstream source description

A flaw was found in the Wildfly Server Role Based Access Control (RBAC) provider. When authorization to control management operations is secured using the Role Based Access Control provider, a user without the required privileges can suspend or resume the server. A user with a Monitor or Auditor role is supposed to have only read access permissions and should not be able to suspend the server. The vulnerability is caused by the Suspend and Resume handlers not performing authorization checks to validate whether the current user has the required permissions to proceed with the action.

Quoted source text, attributed separately from HOL analysis.