CVE-2025-23368

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 43% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

Published

March 4, 2025

Last Modified

September 14, 2026

Advisory Details (4)

Auto-updated May 18, 2026
Patch available. Sources: redhat.
generic

Gruppo TIM | Vulnerability Research & Advisor

https://www.gruppotim.it/it/footer/red-team.html
redhatMentions a patch (unverified)

2337621 – (CVE-2025-23368) CVE-2025-23368 org.wildfly.core:wildfly-elytron-integration: Wildfly Elytron Brute Force Attack via CLI

https://bugzilla.redhat.com/show_bug.cgi?id=2337621
redhatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2025-23368
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Important. A Common

https://access.redhat.com/errata/RHSA-2026:18059

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhateap7-wildfly-0:7.3.18-3.GA_redhat_00001.1.el7eap2026-06-30redhat
redhatwildfly-elytron-integration2026-05-18redhat
redhateap8-wildfly-0:8.1.6-5.GA_redhat_00007.1.el8eap2026-05-18redhat
redhateap8-wildfly-0:8.1.6-5.GA_redhat_00007.1.el9eap2026-05-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.wildfly.core:wildfly-elytron-integration10.0.0.Beta1 ... 9.0.2.Final (293 versions)
  • 32.0.0.Beta1 up to 32.0.0.Beta3: fixed in 32.0.0.Beta3
  • every version up to 31.0.3.Final: fixed in 31.0.3.Final
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 217 total refreshes for this CVE.

  1. 2026-10-09 20:06 UTCEPSS rescore
  2. 2026-10-08 17:09 UTCEPSS rescore
  3. 2026-10-07 23:46 UTCEPSS rescore
  4. 2026-10-06 15:16 UTCEPSS rescore
  5. 2026-10-05 17:42 UTCEPSS rescore
  6. 2026-10-04 08:04 UTCOSV refresh
  7. 2026-10-03 14:24 UTCEPSS rescore
  8. 2026-10-02 16:26 UTCEPSS rescore
  9. 2026-10-01 19:48 UTCEPSS rescore
  10. 2026-09-30 15:02 UTCEPSS rescore
  11. 2026-09-30 15:02 UTCEPSS rescore
  12. 2026-09-28 13:50 UTCEPSS rescore
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-26 15:58 UTCEPSS rescore
  15. 2026-09-26 00:24 UTCEPSS rescore
  16. 2026-09-24 14:02 UTCEPSS rescore
  17. 2026-09-23 13:46 UTCEPSS rescore
  18. 2026-09-22 14:47 UTCEPSS rescore
  19. 2026-09-20 20:15 UTCEPSS rescore
  20. 2026-09-18 19:27 UTCEPSS rescore
  21. 2026-09-16 14:06 UTCEPSS rescore
  22. 2026-09-16 05:13 UTCEPSS rescore
  23. 2026-09-15 03:09 UTCEPSS rescore
  24. 2026-09-14 22:20 UTCVendor advisory
  25. 2026-09-14 21:45 UTCEG score recompute
Show 75 more
  1. 2026-09-14 21:45 UTCVendor advisory
  2. 2026-09-13 16:46 UTCEPSS rescore
  3. 2026-09-12 15:00 UTCEPSS rescore
  4. 2026-09-11 14:51 UTCEPSS rescore
  5. 2026-09-11 09:35 UTCEPSS rescore
  6. 2026-09-10 09:33 UTCEPSS rescore
  7. 2026-09-08 21:59 UTCEPSS rescore
  8. 2026-09-07 16:00 UTCEPSS rescore
  9. 2026-09-06 13:46 UTCEPSS rescore
  10. 2026-09-06 13:46 UTCEPSS rescore
  11. 2026-09-05 15:28 UTCEPSS rescore
  12. 2026-09-04 05:05 UTCEPSS rescore
  13. 2026-09-03 23:16 UTCOSV refresh
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:52 UTCEPSS rescore
  16. 2026-09-01 04:38 UTCEPSS rescore
  17. 2026-08-30 19:16 UTCEPSS rescore
  18. 2026-08-30 01:21 UTCEPSS rescore
  19. 2026-08-28 21:40 UTCEPSS rescore
  20. 2026-08-27 14:24 UTCEPSS rescore
  21. 2026-08-25 13:47 UTCEPSS rescore
  22. 2026-08-23 00:18 UTCEPSS rescore
  23. 2026-08-21 23:48 UTCEPSS rescore
  24. 2026-08-20 22:54 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
  26. 2026-08-18 13:47 UTCEPSS rescore
  27. 2026-08-17 13:46 UTCEPSS rescore
  28. 2026-08-17 12:22 UTCVendor advisory
  29. 2026-08-17 11:51 UTCEG score recompute
  30. 2026-08-17 11:51 UTCVendor advisory
  31. 2026-08-16 14:55 UTCEPSS rescore
  32. 2026-08-16 02:13 UTCEPSS rescore
  33. 2026-08-16 02:13 UTCEPSS rescore
  34. 2026-08-15 01:29 UTCEPSS rescore
  35. 2026-08-13 21:59 UTCEPSS rescore
  36. 2026-08-12 13:50 UTCEPSS rescore
  37. 2026-08-10 23:59 UTCEPSS rescore
  38. 2026-08-09 13:45 UTCEPSS rescore
  39. 2026-08-07 16:26 UTCEPSS rescore
  40. 2026-08-06 13:46 UTCEPSS rescore
  41. 2026-08-05 19:16 UTCEPSS rescore
  42. 2026-08-04 18:26 UTCVendor advisory
  43. 2026-08-04 18:01 UTCEG score recompute
  44. 2026-08-04 18:01 UTCVendor advisory
  45. 2026-08-04 15:09 UTCEPSS rescore
  46. 2026-08-04 13:27 UTCVendor advisory
  47. 2026-08-04 12:36 UTCVendor advisory
  48. 2026-08-04 11:24 UTCVendor advisory
  49. 2026-08-04 11:16 UTCEG score recompute
  50. 2026-08-04 11:16 UTCVendor advisory
  51. 2026-08-04 10:37 UTCEPSS rescore
  52. 2026-08-04 09:45 UTCVendor advisory
  53. 2026-08-04 08:19 UTCVendor advisory
  54. 2026-08-04 07:32 UTCEG score recompute
  55. 2026-08-04 07:32 UTCVendor advisory
  56. 2026-08-03 10:35 UTCEPSS rescore
  57. 2026-08-02 02:25 UTCEPSS rescore
  58. 2026-08-01 04:15 UTCEPSS rescore
  59. 2026-07-30 16:27 UTCEPSS rescore
  60. 2026-07-30 01:29 UTCEPSS rescore
  61. 2026-07-28 15:35 UTCEPSS rescore
  62. 2026-07-28 00:54 UTCOSV refresh
  63. 2026-07-27 14:12 UTCEPSS rescore
  64. 2026-07-26 14:53 UTCEPSS rescore
  65. 2026-07-25 14:17 UTCEPSS rescore
  66. 2026-07-24 14:17 UTCEPSS rescore
  67. 2026-07-23 14:17 UTCEPSS rescore
  68. 2026-07-23 02:51 UTCEG score recompute
  69. 2026-07-22 14:07 UTCEPSS rescore
  70. 2026-07-22 14:07 UTCEPSS rescore
  71. 2026-07-21 15:24 UTCEPSS rescore
  72. 2026-07-20 17:07 UTCEPSS rescore
  73. 2026-07-19 14:30 UTCEPSS rescore
  74. 2026-07-19 14:30 UTCEPSS rescore
  75. 2026-07-19 02:28 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-23368?
CVE-2025-23368 is a high vulnerability published on March 4, 2025. 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.
When was CVE-2025-23368 disclosed?
CVE-2025-23368 was first published on March 4, 2025, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-23368 actively exploited?
CVE-2025-23368 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-23368?
CVE-2025-23368 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-23368?
A fix for CVE-2025-23368 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-23368 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-23368

Explore →

Is Your Infrastructure Affected by CVE-2025-23368?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.