CVE-2025-23368 is a high-severity (CVSS 8.1) CWE-307 vulnerability in org.wildfly.core:wildfly-elytron-integration. A fix is available for org.wildfly.core:wildfly-elytron-integration — see the affected versions and patch details below.
Org.wildfly.core:wildfly-elytron-integration: wildfly elytron brute force attack via cli
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-23368.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-23368 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.wildfly.core:wildfly-elytron-integration☕org.wildfly.core:wildfly-elytron-integrationReal-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
Impact
A flaw was found in Wildfly Elytron integration. The component does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks via CLI.
Patches
The default behaviour has been changed in WildFly Core 31.0.3.Final, and 32.0.0.Beta3 - the first version is used by WildFly 39.0.1.Final and the second will be included in WildFly 40.
Workarounds
No direct workaround. Monitoring network traffic / blocking suspicious traffic may help.
References
https://www.cve.org/CVERecord?id=CVE-2025-23368 https://issues.redhat.com/browse/WFCORE-7192
Acknowledgements
We 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.wildfly.core:wildfly-elytron-integration | ≥ 32.0.0.Beta1&&< 32.0.0.Beta3 | 32.0.0.Beta3org.wildfly.core:wildfly-elytron-integration:32.0.0.Beta3 |
| ☕Maven | org.wildfly.core:wildfly-elytron-integration | all versions | 31.0.3.Finalorg.wildfly.core:wildfly-elytron-integration:31.0.3.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly.core:wildfly-elytron-integration, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.wildfly.core:wildfly-elytron-integration to 32.0.0.Beta3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-23368 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-23368 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-23368. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
According to WildFly Elytron, this affects all versions of JBoss EAP from version 7.1. Red Hat build of Keycloak does not ship wildfly-elytron.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | eap7-wildfly-0:7.3.18-3.GA_redhat_00001.1.el7eap | RHSA-2026:33371 |
| Red Hat JBoss Enterprise Application Platform 8.1.7.GA | org.wildfly.core/wildfly-elytron-integration:27.1.11.Final-redhat-00001 | RHSA-2026:18059 |
| Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8 | eap8-wildfly-0:8.1.6-5.GA_redhat_00007.1.el8eap | RHSA-2026:18054 |
| Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 9 | eap8-wildfly-0:8.1.6-5.GA_redhat_00007.1.el9eap | RHSA-2026:18055 |
Frequently Asked Questions
Is CVE-2025-23368 in your dependencies?
O3 Security finds CVE-2025-23368 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.