Summary
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.
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.
CVE-2025-23368 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (32.0.0.Beta3, 31.0.3.Final); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
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.
Frequently Asked Questions
- What is CVE-2025-23368? CVE-2025-23368 is a high-severity security vulnerability in org.wildfly.core:wildfly-elytron-integration (maven), affecting versions >= 32.0.0.Beta1, < 32.0.0.Beta3. It is fixed in 32.0.0.Beta3, 31.0.3.Final.
- How severe is CVE-2025-23368? CVE-2025-23368 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.wildfly.core:wildfly-elytron-integration are affected by CVE-2025-23368? org.wildfly.core:wildfly-elytron-integration (maven) versions >= 32.0.0.Beta1, < 32.0.0.Beta3 is affected.
- Is there a fix for CVE-2025-23368? Yes. CVE-2025-23368 is fixed in 32.0.0.Beta3, 31.0.3.Final. Upgrade to this version or later.
- Is CVE-2025-23368 exploitable, and should I be worried? Whether CVE-2025-23368 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-23368 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-23368?
- Upgrade
org.wildfly.core:wildfly-elytron-integrationto 32.0.0.Beta3 or later - Upgrade
org.wildfly.core:wildfly-elytron-integrationto 31.0.3.Final or later
- Upgrade