CVE-2025-23368 — Org.wildfly.core:wildfly-elytron-integration: wildfly elytron brute force attack via cli
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.9% (30-day exploitation probability)+9
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Maven Org.wildfly.core:wildfly-elytron-integration: fixed in version 32.0.0.Beta3 — github.com (GitHub Security Advisories)
- Maven Org.wildfly.core:wildfly-elytron-integration: fixed in version 31.0.3.Final — github.com (GitHub Security Advisories)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Red Hat Data Grid, Red Hat Jboss Enterprise Application Platform, Red Hat Red Hat Data Grid 8…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Red Hat | Data Grid | version 8.0 | Vulnerable | NIST National Vulnerability Database |
| Red Hat | Jboss Enterprise Application Platform | version 7.0.0version 8.0.0 | Vulnerable | NIST National Vulnerability Database |
| Red Hat | Red Hat Data Grid 8 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat Fuse 7 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat JBoss Enterprise Application Platform 7 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 9 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat Process Automation 7 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Red Hat Single Sign-On 7 | versions not specified by the source | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Red Hat | Wildfly Core | < 31.0.3 | Vulnerable | NIST National Vulnerability Database |
| Maven | Org.wildfly.core:wildfly-elytron-integration | ≥ 32.0.0.Beta1 and < 32.0.0.Beta3< 31.0.3.Final | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.1 | CVSS 3.1 | High | 2.2 | 5.9 | secalert@redhat.com via NIST National Vulnerability Database |
| 8.1 | CVSS 3.1 | High | 2.2 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 8.1 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.1 | CVSS 3.1 | High | — | — | redhat via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CWE-307 · Improper Restriction of Excessive Authentication Attempts
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · maven/org.wildfly.core:wildfly-elytron-integration
- Affected products added · red hat/red hat jboss enterprise application platform 7.3 eus for rhel 7, red hat/red hat jboss enterprise application p
- SSVC assessment updated
- Record published
- Affected products added · redhat/wildfly core, redhat/data grid, redhat/jboss enterprise application platform
- CVSS changed · 8.1
- Source status changed · → Modified
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
14 on the record
- bugzilla.redhat.com/show_bug.cgi
- access.redhat.com/security/cve/CVE-2025-23368
- github.com/wildfly/wildfly-core/pull/6634
- nvd.nist.gov/vuln/detail/CVE-2025-23368
- github.com/wildfly/wildfly-core/security/advisories/GHSA-qhp6-6p8p-2rqh
- access.redhat.com/errata/RHSA-2026:18054
- github.com/wildfly/wildfly-core/commit/a6f9d7534aa44de741337756f8377ad3a81f7695
- access.redhat.com/errata/RHSA-2026:18059
- www.gruppotim.it/it/footer/red-team.html
- github.com/wildfly/wildfly-core/pull/6635
- github.com/wildfly/wildfly-core/commit/11e873031c522a0b36afb59880ce4dd59efd0bc0
- access.redhat.com/errata/RHSA-2026:33371
- access.redhat.com/errata/RHSA-2026:18055
- github.com/advisories/GHSA-qhp6-6p8p-2rqh
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-85634 Wildfly-core: wildfly-core: deployer rbac role privilege escalation via path traversal in deployment name 4h
- Medium CVE-2026-93574 Io.netty/netty-codec-http: netty: http request smuggling via post-digit whitespace in chunk-size parsing 27d
- Medium CVE-2026-93562 Io.netty/netty-codec-http: netty: incomplete validation of malformed transfer-encoding allows http request smuggling 27d
- Medium CVE-2026-93432 Io.quarkus.qute:quarkus-core: cross-site scripting (xss) and json injection via qute {#eval} section in quarkus 27d
- Medium CVE-2026-93579 Io.netty/netty-codec-http2: netty: http/2 header field values are not validated by default (cr/lf/nul passthrough) 27d
- Medium CVE-2026-93573 Io.netty/netty-codec-http: netty split transfer-encoding fields bypass final-chunked validation and enable request smuggling 27d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-23368 is "Org.wildfly.core:wildfly-elytron-integration: wildfly elytron brute force attack via cli", rated High. It affects Data Grid (Red Hat); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.1 describes technical severity. EPSS 0.89% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.