VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.wildfly.common:wildfly-common: vulnerability history, versions and safety

org.wildfly.common:wildfly-common is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

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.common:wildfly-common vulnerabilities

Vulert verdict on org.wildfly.common:wildfly-common 2.0.1 i

Updated on 23 Oct 2026

Good news: 2.0.1, the version you would install today, has no known vulnerabilities.

Package health score 67/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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

  • Current release 2.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 5,444 packages i
  • Stars 16 i
  • OpenSSF scorecard 3/10 i
  • Last release 24 months ago 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.common:wildfly-common, 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
2.0.1 25 Sep 2024 none Apache-2.0 — Details →
2.0.0 07 May 2024 none Apache-2.0 — Details →
1.7.0.Final 02 Nov 2023 none Apache-2.0 — Details →
1.6.0.Final 07 Mar 2022 none Apache-2.0 — Details →
1.5.4.Final-format-002 16 Feb 2022 none Apache-2.0 — Details →
1.5.4.Final-format-001 06 Mar 2020 none Apache-2.0 — Details →
1.5.4.Final 06 Mar 2020 none Apache-2.0 — Details →
1.5.3.Final-format-001 31 Jan 2020 none Apache-2.0 — Details →
1.5.3.Final 31 Jan 2020 none Apache-2.0 — Details →
1.5.2.Final 26 Jun 2019 none Apache-2.0 — Details →
1.5.1.Final 15 Apr 2019 none Apache-2.0 — Details →
1.5.0.Final-format-001 28 Feb 2019 none Apache-2.0 — Details →
1.5.0.Final 27 Feb 2019 none Apache-2.0 — Details →
1.5.0.Alpha4-format-002 11 Feb 2019 none Apache-2.0 — Details →
1.5.0.Alpha4-format-001 11 Feb 2019 none Apache-2.0 — Details →
1.5.0.Alpha4 12 Dec 2018 none Apache-2.0 — Details →
1.2.1.Final 29 Nov 2018 none Apache-2.0 — Details →
1.5.0.Alpha3-format-001 15 Nov 2018 none Apache-2.0 — Details →
1.5.0.Alpha3 15 Nov 2018 none Apache-2.0 — Details →
1.5.0.Alpha2-format-001 14 Nov 2018 none Apache-2.0 — Details →
1.5.0.Alpha2 14 Nov 2018 none Apache-2.0 — Details →
1.5.0.Alpha1-format-002 10 Oct 2018 none Apache-2.0 — Details →
1.5.0.Alpha1-format-001 10 Oct 2018 none — — Details →
1.5.0.Alpha1 03 Oct 2018 none Apache-2.0 — Details →
1.4.0.Final 11 May 2018 none Apache-2.0 — Details →
1.3.2.Final 01 May 2018 none Apache-2.0 — Details →
1.3.1.Final 16 Mar 2018 none Apache-2.0 — Details →
1.3.0.Final 11 Jan 2018 none Apache-2.0 — Details →
1.3.0.Beta2 08 Dec 2017 none Apache-2.0 — Details →
1.3.0.Beta1 01 Nov 2017 none Apache-2.0 — Details →
1.2.0.Final 10 Aug 2017 none Apache-2.0 — Details →
1.2.0.CR1 21 Jun 2017 none non-standard — Details →
1.2.0.Beta11 05 Jun 2017 none non-standard — Details →
1.2.0.Beta10 20 Apr 2017 none non-standard — Details →
1.2.0.Beta9 01 Apr 2017 none non-standard — Details →
1.2.0.Beta8 13 Mar 2017 none non-standard — Details →
1.2.0.Beta7 02 Mar 2017 none non-standard — Details →
1.2.0.Beta6 22 Feb 2017 none non-standard — Details →
1.2.0.Beta5 30 Jan 2017 none non-standard — Details →
1.2.0.Beta4 25 Jan 2017 none non-standard — Details →
1.2.0.Beta3 20 Dec 2016 none non-standard — Details →
1.2.0.Beta2 07 Dec 2016 none non-standard — Details →
1.2.0.Beta1 28 Mar 2016 none non-standard — Details →
1.1.0.Final 18 Sep 2015 none non-standard — Details →
1.0.0.Final 03 Sep 2015 none non-standard — Details →
1.0.0.Alpha3 17 Jun 2015 none non-standard — Details →
1.0.0.Alpha2 06 Mar 2015 none non-standard — Details →
1.0.0.Alpha1 20 Feb 2015 none non-standard — Details →

All 48 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for org.wildfly.common:wildfly-common

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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.common:wildfly-common

Is org.wildfly.common:wildfly-common safe to use?

Vulert has no vulnerabilities on record for org.wildfly.common:wildfly-common in Maven at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

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

Vulert scores org.wildfly.common:wildfly-common 67/100, which reads as usable, but worth attention. 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.common:wildfly-common affected?

No. 2.0.1, 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.

Which version of org.wildfly.common:wildfly-common should I use?

2.0.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.wildfly.common:wildfly-common have?

0 vulnerabilities are recorded for org.wildfly.common:wildfly-common in the Maven ecosystem: 0 critical, 0 high, 0 medium and 0 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.common:wildfly-common vulnerabilities disclosed?

0 vulnerabilities were recorded for org.wildfly.common:wildfly-common in the last 12 months. 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.common:wildfly-common 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.common:wildfly-common for upcoming vulnerabilities?

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