How severe is CVE-2025-23367?

CVE-2025-23367 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-23367?

CVE-2025-23367 affects the following packages: org.wildfly.core:wildfly-server (Maven), org.wildfly.core:wildfly-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-23367?

Update org.wildfly.core:wildfly-server to 27.0.1.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-23367 is resolved across your whole dependency graph.

How do I detect CVE-2025-23367 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly.core:wildfly-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-23367 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2025-23367 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-23367 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-23367?

CVE-2025-23367 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-23367?

CVE-2025-23367 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-23367 published, and has it been updated?

CVE-2025-23367 was published on January 30, 2025 and was last updated on November 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2025-23367 — wildfly-server

MEDIUM

CVE-2025-23367 is a medium-severity (CVSS 6.5) CWE-284 vulnerability in org.wildfly.core:wildfly-server. A fix is available for org.wildfly.core:wildfly-server — see the affected versions and patch details below.

Org.wildfly.core:wildfly-server: wildfly improper rbac permission

Also known asBIT-wildfly-2025-23367GHSA-qr6x-62gq-4ccp

Published

Jan 30, 2025

Updated

Nov 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-23367.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk-0.01%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.wildfly.core:wildfly-server☕org.wildfly.core:wildfly-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Impact

Standalone server (Domain mode is not affected) with use access control enabled with RBAC provider can be suspended or resumed by unauthorized users. When a server is suspended, the server will stop receiving user requests. The resume handle does the opposite; it will cause a suspended server to start accepting user requests.

Patches

Fixed in WildFly Core 27.0.1.Final

Workarounds

No workaround available

References

Acknowledgements

The WildFly project would like to thank Claudia Bartolini (TIM S.p.A), Marco Ventura (TIM S.p.A), and Massimiliano Brolli (TIM S.p.A) for reporting this issue. https://www.gruppotim.it/it/footer/red-team.html

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.wildfly.core:wildfly-server`	all versions	27.0.1.Final`org.wildfly.core:wildfly-server:27.0.1.Final`
☕Maven	`org.wildfly.core:wildfly-server`	≥ 28.0.0.Beta1&&< 28.0.0.Beta2	28.0.0.Beta2`org.wildfly.core:wildfly-server:28.0.0.Beta2`

Affected Products

2 products · 4 configurations

Application

jboss enterprise application platformredhat

≥ 8.0.0 && < 8.0.7

range

Application

wildflyredhat

< 27.0.1

1 version

28.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly.core:wildfly-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.wildfly.core:wildfly-server to 27.0.1.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-23367 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat has evaluated this issue and the attacker must be authenticated as a user that belongs to the "Monitor" or "Auditor" management groups. It requires previous privileges to jeopardize an environment.

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2025-23367 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat JBoss Enterprise Application Platform	`org.wildfly.core/wildfly-server:15.0.45.Final-redhat-00001`	RHSA-2025:3467
Red Hat JBoss Enterprise Application Platform 7.4.22	`org.wildfly.core/wildfly-server:15.0.42.Final-redhat-00001`	RHSA-2025:4552
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8	`eap7-netty-0:4.1.119-1.Final_redhat_00004.1.el8eap`	RHSA-2025:3465
Red Hat JBoss Enterprise Application Platform 8	`wildfly-server`	RHSA-2025:3992
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8	`eap8-apache-commons-io-0:2.16.1-1.redhat_00001.1.el8eap`	RHSA-2025:3989
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 9	`eap8-apache-commons-io-0:2.16.1-1.redhat_00001.1.el9eap`	RHSA-2025:3990

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-23367 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works