# Wildfly Elytron integration susceptible to brute force attacks via CLI Advisory record · `GHSA-qhp6-6p8p-2rqh` - **Identifiers:** `GHSA-qhp6-6p8p-2rqh` · `CVE-2025-23368` - **State:** Confirmed - **Severity:** CVSS 8.1 High - **Critical:** No - **Weakness (CWE):** [CWE-307](https://cwe.mitre.org/data/definitions/307.html) - **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) - **Published:** 13 Feb 2026 - **Updated:** 13 Feb 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 13 Feb 2026, 20:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.wildfly.core:wildfly-elytron-integration` (Maven): affected `>=32.0.0.Beta1, <32.0.0.Beta3 || <31.0.3.Final`; fixed in `32.0.0.Beta3`, `31.0.3.Final` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The Maven package org.wildfly.core:wildfly-elytron-integration, in versions from 32.0.0.Beta1 up to but not including 32.0.0.Beta3, and in versions before 31.0.3.Final, does not sufficiently limit repeated failed authentication attempts made through the CLI. An attacker with access to the CLI can therefore carry out brute force attacks against credentials. Upgrade to 32.0.0.Beta3 or 31.0.3.Final; the source gives no workaround beyond monitoring and blocking suspicious network traffic. Written 3 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (redhat) - **CISA KEV:** Not listed. - **EPSS:** 0.0089, the 59th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 4 Mar 2025, 15:14 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-23368) - 4 Mar 2025, 16:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-23368) - 31 Oct 2026, 14:21 UTC: First seen by agentprime - 31 Oct 2026, 14:21 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qhp6-6p8p-2rqh) ## Sources - [GitHub Advisory Database: GHSA-qhp6-6p8p-2rqh](https://github.com/advisories/GHSA-qhp6-6p8p-2rqh) - [OSV: GHSA-qhp6-6p8p-2rqh](https://osv.dev/vulnerability/GHSA-qhp6-6p8p-2rqh) - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .