Credential compromise via missing failed-attempt throttling
Published Mar 4, 2025 · Updated Aug 17, 2026
Improper restriction of authentication attempts in WildFly Core allows remote attackers to brute-force credentials over HTTP or SASL. Elytron security realms accept repeated password guesses without tracking failures, throttling attempts, or temporarily disabling the targeted identity. Exposure requires network access to an authentication port, and success grants the access associated with a guessed account.
Summary
What happened
Improper restriction of authentication attempts in WildFly Core allows remote attackers to brute-force credentials over HTTP or SASL. Elytron security realms accept repeated password guesses without tracking failures, throttling attempts, or temporarily disabling the targeted identity. Exposure requires network access to an authentication port, and success grants the access associated with a guessed account.
The record
- CVE
- CVE-2025-23368
- Published
- Mar 4, 2025
- Updated
- Aug 17, 2026
- Vendor
- WildFly
- Product
- WildFly Core
- Classifications
- CWE-307, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 4, 2025CVE publishedPublication date reported by the CVE source.
- Aug 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo