# CVE-2025-23368: Org.wildfly.core:wildfly-elytron-integration: wildfly elytron brute force attack via cli

> Attackers can bypass brute force protections in WildFly Elytron via CLI, potentially leading to account takeover through repeated authentication attempts.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Mar 2025
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-qhp6-6p8p-2rqh

## What is CVE-2025-23368?

CVE-2025-23368 is a high-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 4 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2025-23368?

4 open source packages ship an affected version, including org.wildfly.core:wildfly-elytron-integration. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.wildfly.core:wildfly-elytron-integration` | Maven | All versions | 31.0.3.Final |
| `org.wildfly.core:wildfly-elytron-integration` | Maven | All versions | 31.0.3.Final |
| `org.wildfly.core:wildfly-elytron-integration` | Maven | From 32.0.0.Beta1 | 32.0.0.Beta3 |
| `org.wildfly.core:wildfly-elytron-integration` | Maven | From 32.0.0.Beta1 | 32.0.0.Beta3 |

Products: Redhat Data Grid, Redhat Jboss Enterprise Application Platform, Redhat Wildfly Core.

## How do I fix CVE-2025-23368?

Upgrade org.wildfly.core:wildfly-elytron-integration to a fixed version for your release line: 31.0.3.Final or 32.0.0.Beta3.

## Is CVE-2025-23368 being exploited?

There is no known exploitation of CVE-2025-23368 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2015-7501](https://insights.sbomify.com/CVE-2015-7501/): Deserialization of Untrusted Data in Apache commons collections (critical 9.8)
- [CVE-2019-14838](https://insights.sbomify.com/CVE-2019-14838/): Wildfly Authorization Misconfiguration (medium 5.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23368 and fix it if it is affected.

What it is: CVE-2025-23368 is a high-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 4 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23368 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.wildfly.core:wildfly-elytron-integration (Maven): affected all versions; fixed in 31.0.3.Final
- org.wildfly.core:wildfly-elytron-integration (Maven): affected all versions; fixed in 31.0.3.Final
- org.wildfly.core:wildfly-elytron-integration (Maven): affected from 32.0.0.Beta1; fixed in 32.0.0.Beta3
- org.wildfly.core:wildfly-elytron-integration (Maven): affected from 32.0.0.Beta1; fixed in 32.0.0.Beta3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-23368/ (Markdown: https://insights.sbomify.com/CVE-2025-23368/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23368
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23368
- OSV: https://osv.dev/vulnerability/CVE-2025-23368

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-23368/
Summaries are generated and may contain mistakes; the official description above is the record.