VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.wildfly.core:wildfly-server: vulnerability history, versions and safety

org.wildfly.core:wildfly-server is a package in the Maven ecosystem. Vulert records 3 vulnerabilities for it across 66 releases, from May 2022 to Jan 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M2 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.wildfly.core:wildfly-server vulnerabilities

Vulert verdict on org.wildfly.core:wildfly-server 34.0.0.Final i

Updated on 23 Oct 2026

Good news: 34.0.0.Final, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 34.0.0.Final or newer. This can change: a vulnerability disclosed tomorrow can affect 34.0.0.Final too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 34.0.0.Final — unaffected i
  • Vulnerabilities on record 3 over 2 years · 0 in the last year i
  • Latest disclosure 31 Jan 2025 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 28 packages i
  • Stars 201 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.wildfly.core:wildfly-server, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
34.0.0.Final 20 Oct 2026 none Apache-2.0 — Details →
34.0.0.Beta7 07 Oct 2026 none Apache-2.0 — Details →
34.0.0.Beta6 24 Sep 2026 none Apache-2.0 — Details →
34.0.0.Beta5 17 Sep 2026 none Apache-2.0 — Details →
33.0.1.Final 28 Aug 2026 none Apache-2.0 — Details →
34.0.0.Beta4 28 Aug 2026 none Apache-2.0 — Details →
34.0.0.Beta3 31 Jul 2026 none Apache-2.0 — Details →
34.0.0.Beta2 30 Jul 2026 none Apache-2.0 — Details →
34.0.0.Beta1 28 Jul 2026 none Apache-2.0 — Details →
33.0.0.Final 14 Jul 2026 none Apache-2.0 — Details →
33.0.0.Beta5 04 Jul 2026 none Apache-2.0 — Details →
33.0.0.Beta4 24 Jun 2026 none Apache-2.0 — Details →
33.0.0.Beta3 18 Jun 2026 none Apache-2.0 — Details →
32.0.2.Final 16 Jun 2026 none Apache-2.0 — Details →
32.0.1.Final 15 Jun 2026 none Apache-2.0 — Details →
33.0.0.Beta2 06 Jun 2026 none Apache-2.0 — Details →
33.0.0.Beta1 28 May 2026 none Apache-2.0 — Details →
32.0.0.Final 11 May 2026 none Apache-2.0 — Details →
32.0.0.Beta7 14 Apr 2026 none Apache-2.0 — Details →
32.0.0.Beta6 27 Mar 2026 none Apache-2.0 — Details →
32.0.0.Beta5 13 Mar 2026 none Apache-2.0 — Details →
32.0.0.Beta4 20 Feb 2026 none Apache-2.0 — Details →
32.0.0.Beta3 14 Feb 2026 none Apache-2.0 — Details →
31.0.3.Final 09 Feb 2026 none Apache-2.0 — Details →
31.0.2.Final 07 Feb 2026 none Apache-2.0 — Details →
32.0.0.Beta2 29 Jan 2026 none Apache-2.0 — Details →
32.0.0.Beta1 23 Jan 2026 none Apache-2.0 — Details →
31.0.1.Final 16 Jan 2026 none Apache-2.0 — Details →
31.0.0.Final 14 Jan 2026 none Apache-2.0 — Details →
31.0.0.Beta3 12 Dec 2025 none Apache-2.0 — Details →
31.0.0.Beta2 17 Nov 2025 none Apache-2.0 — Details →
31.0.0.Beta1 29 Oct 2025 none Apache-2.0 — Details →
30.0.0.Final 11 Oct 2025 none Apache-2.0 — Details →
30.0.0.Beta4 03 Oct 2025 none Apache-2.0 — Details →
30.0.0.Beta3 26 Sep 2025 none Apache-2.0 — Details →
30.0.0.Beta2 23 Sep 2025 none Apache-2.0 — Details →
30.0.0.Beta1 23 Sep 2025 none Apache-2.0 — Details →
29.0.1.Final 03 Sep 2025 none Apache-2.0 — Details →
29.0.0.Final 08 Aug 2025 none Apache-2.0 — Details →
29.0.0.Beta6 23 Jun 2025 none Apache-2.0 — Details →
29.0.0.Beta5 19 Jun 2025 none Apache-2.0 — Details →
29.0.0.Beta4 12 Jun 2025 none Apache-2.0 — Details →
29.0.0.Beta3 26 May 2025 none Apache-2.0 — Details →
29.0.0.Beta2 15 May 2025 none Apache-2.0 — Details →
28.0.1.Final 08 May 2025 none Apache-2.0 — Details →
29.0.0.Beta1 30 Apr 2025 none Apache-2.0 — Details →
28.0.0.Final 07 Apr 2025 none Apache-2.0 — Details →
28.0.0.Beta6 27 Mar 2025 none Apache-2.0 — Details →
28.0.0.Beta5 21 Mar 2025 none Apache-2.0 — Details →
28.0.0.Beta4 07 Mar 2025 none Apache-2.0 — Details →
28.0.0.Beta3 13 Feb 2025 none Apache-2.0 — Details →
28.0.0.Beta2 13 Feb 2025 none Apache-2.0 — Details →
27.0.1.Final 31 Jan 2025 none Apache-2.0 — Details →
28.0.0.Beta1 22 Jan 2025 none Apache-2.0 — Details →
27.0.0.Final 23 Dec 2024 M1 Apache-2.0 Yes Details →
27.0.0.Beta7 19 Dec 2024 M1 Apache-2.0 Yes Details →
27.0.0.Beta6 16 Dec 2024 M1 Apache-2.0 Yes Details →
27.0.0.Beta5 09 Dec 2024 M1 Apache-2.0 Yes Details →
27.0.0.Beta4 29 Nov 2024 M1 Apache-2.0 Yes Details →
27.0.0.Beta3 21 Nov 2024 M1 Apache-2.0 Yes Details →
27.0.0.Beta2 30 Oct 2024 M1 Apache-2.0 Yes Details →
27.0.0.Beta1 18 Oct 2024 M1 Apache-2.0 Yes Details →
26.0.1.Final 16 Oct 2024 M1 Apache-2.0 Yes Details →
26.0.0.Final 07 Oct 2024 M1 Apache-2.0 Yes Details →
26.0.0.Beta5 23 Sep 2024 M1 Apache-2.0 Yes Details →
26.0.0.Beta4 13 Sep 2024 M1 Apache-2.0 Yes Details →
25.0.2.Final 05 Sep 2024 M1 Apache-2.0 Yes Details →
26.0.0.Beta3 29 Aug 2024 M1 Apache-2.0 Yes Details →
26.0.0.Beta2 21 Aug 2024 M1 Apache-2.0 Yes Details →
25.0.1.Final 19 Aug 2024 M1 Apache-2.0 Yes Details →
26.0.0.Beta1 24 Jul 2024 M1 Apache-2.0 Yes Details →
25.0.0.Final 17 Jul 2024 M1 Apache-2.0 Yes Details →
25.0.0.Beta5 01 Jul 2024 M1 Apache-2.0 Yes Details →
25.0.0.Beta4 20 Jun 2024 M1 Apache-2.0 Yes Details →
25.0.0.Beta3 06 Jun 2024 M1 Apache-2.0 Yes Details →
24.0.1.Final 28 May 2024 M1 Apache-2.0 Yes Details →
25.0.0.Beta2 15 May 2024 M1 Apache-2.0 Yes Details →
25.0.0.Beta1 06 May 2024 M1 Apache-2.0 Yes Details →
24.0.0.Final 23 Apr 2024 M1 Apache-2.0 Yes Details →
24.0.0.Beta3 26 Mar 2024 M1 Apache-2.0 Yes Details →
24.0.0.Beta2 28 Feb 2024 M1 Apache-2.0 Yes Details →
23.0.3.Final 21 Feb 2024 M1 Apache-2.0 Yes Details →
23.0.2.Final 19 Feb 2024 M1 Apache-2.0 Yes Details →
24.0.0.Beta1 15 Feb 2024 M1 Apache-2.0 Yes Details →
23.0.1.Final 23 Jan 2024 M1 Apache-2.0 Yes Details →
23.0.0.Final 22 Jan 2024 M1 Apache-2.0 Yes Details →
23.0.0.Beta5 10 Jan 2024 M1 Apache-2.0 Yes Details →
23.0.0.Beta4 18 Dec 2023 M1 Apache-2.0 Yes Details →
23.0.0.Beta3 09 Dec 2023 M1 Apache-2.0 Yes Details →
22.0.2.Final 28 Nov 2023 M1 Apache-2.0 Yes Details →
23.0.0.Beta2 22 Nov 2023 M1 Apache-2.0 Yes Details →
23.0.0.Beta1 31 Oct 2023 M1 Apache-2.0 Yes Details →
22.0.1.Final 18 Oct 2023 M1 Apache-2.0 Yes Details →
22.0.0.Final 09 Oct 2023 M1 Apache-2.0 Yes Details →
22.0.0.Beta3 25 Sep 2023 M1 Apache-2.0 Yes Details →
22.0.0.Beta2 14 Sep 2023 M1 LGPL-2.1-or-later Yes Details →
21.1.1.Final 23 Aug 2023 M1 LGPL-2.1-or-later Yes Details →
22.0.0.Beta1 09 Aug 2023 M1 LGPL-2.1-or-later Yes Details →
21.1.0.Final 17 Jul 2023 M1 LGPL-2.1-or-later Yes Details →
21.1.0.Beta2 03 Jul 2023 M1 LGPL-2.1-or-later Yes Details →
21.1.0.Beta1 26 Jun 2023 M1 — Yes Details →
21.0.0.Beta4 16 Jun 2023 M1 — Yes Details →
21.0.0.Beta3 12 Jun 2023 M1 — Yes Details →
21.0.0.Beta2 07 Jun 2023 M1 — Yes Details →
21.0.0.Beta1 30 May 2023 M1 — Yes Details →
20.0.2.Final 16 May 2023 M1 — Yes Details →
20.0.1.Final 17 Apr 2023 M1 — Yes Details →
20.0.0.Final 05 Apr 2023 M1 — Yes Details →
20.0.0.Beta8 24 Mar 2023 M1 — Yes Details →
20.0.0.Beta7 08 Mar 2023 M1 — Yes Details →
20.0.0.Beta6 15 Feb 2023 M1 — Yes Details →
20.0.0.Beta5 17 Jan 2023 M1 — Yes Details →
19.0.1.Final 13 Dec 2022 M1 — Yes Details →
20.0.0.Beta4 07 Dec 2022 M1 — Yes Details →
20.0.0.Beta3 23 Nov 2022 M1 — Yes Details →
20.0.0.Beta2 07 Nov 2022 M1 — Yes Details →
20.0.0.Beta1 04 Nov 2022 M1 — Yes Details →
19.0.0.Final 19 Oct 2022 M1 — Yes Details →
19.0.0.Beta18 19 Sep 2022 M1 — Yes Details →
19.0.0.Beta17 12 Sep 2022 M1 — Yes Details →

The newest 120 of 446 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.wildfly.core:wildfly-server

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-23367: WildFly Server RBAC Misconfiguration Allows Unauthorized Server Control 6.5 medium 27.0.1.Final 31 Jan 2025
CVE-2018-10862: Improper Limitation of a Pathname to a Restricted Directory in WildFly 5.5 medium 6.0.0.Alpha3 14 May 2022
CVE-2021-3644: Wildfly-core Vault Expression Access Vulnerability 3.3 low 16.0.1.Final 27 Aug 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.wildfly.core:wildfly-server

Is org.wildfly.core:wildfly-server safe to use?

Vulert records 3 vulnerabilities for org.wildfly.core:wildfly-server in Maven: 0 critical, 0 high, 2 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.wildfly.core:wildfly-server's Vulert package health score?

Vulert scores org.wildfly.core:wildfly-server 77/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.wildfly.core:wildfly-server affected?

No. 34.0.0.Final, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does org.wildfly.core:wildfly-server have?

3 vulnerabilities are recorded for org.wildfly.core:wildfly-server in the Maven ecosystem: 0 critical, 0 high, 2 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.wildfly.core:wildfly-server vulnerabilities disclosed?

0 vulnerabilities were recorded for org.wildfly.core:wildfly-server in the last 12 months, and the oldest entry in this database dates to 14 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.wildfly.core:wildfly-server are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.wildfly.core:wildfly-server for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.wildfly.core:wildfly-server version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.