Vulnerability Database · Maven · Package report

org.slf4j:slf4j-api: vulnerability history, versions and safety

Q: How do I monitor org.slf4j:slf4j-api for upcoming vulnerabilities?

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

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

0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.slf4j:slf4j-api vulnerabilities

Vulert verdict on org.slf4j:slf4j-api 2.1.0-alpha1 i

Updated on 23 Oct 2026

Good news: 2.1.0-alpha1, the version you would install today, has no known vulnerabilities.

Package health score 71/100

Security Minor issues
Maintenance Slowing
Popularity Key ecosystem project
Community Moderate

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

Current release 2.1.0-alpha1 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 1,710 packages i
Stars 2,530 i
OpenSSF scorecard 4/10 i
Last release 33 months ago i
Licence MIT 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for org.slf4j:slf4j-api, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
2.0.20	23 Sep 2026	none	MIT	—	Details →
2.0.19	04 Sep 2026	none	MIT	—	Details →
2.0.18	12 May 2026	none	MIT	—	Details →
2.0.17	25 Feb 2025	none	MIT	—	Details →
2.0.16	10 Aug 2024	none	MIT	—	Details →
2.0.15	08 Aug 2024	none	MIT	—	Details →
2.0.14	06 Aug 2024	none	MIT	—	Details →
2.0.13	12 Apr 2024	none	MIT	—	Details →
2.0.12	05 Feb 2024	none	MIT	—	Details →
2.0.11	08 Jan 2024	none	MIT	—	Details →
2.1.0-alpha1	02 Jan 2024	none	MIT	—	Details →
2.0.10	28 Dec 2023	none	MIT	—	Details →
2.1.0-alpha0	28 Dec 2023	none	MIT	—	Details →
2.0.9	03 Sep 2023	none	MIT	—	Details →
2.0.8	03 Sep 2023	none	MIT	—	Details →
2.0.7	17 Mar 2023	none	MIT	—	Details →
2.0.6	12 Dec 2022	none	MIT	—	Details →
2.0.5	25 Nov 2022	none	MIT	—	Details →
2.0.4	17 Nov 2022	none	MIT	—	Details →
2.0.3	28 Sep 2022	none	MIT	—	Details →
2.0.2	20 Sep 2022	none	MIT	—	Details →
2.0.1	14 Sep 2022	none	MIT	—	Details →
2.0.0	20 Aug 2022	none	MIT	—	Details →
2.0.0-beta1	06 Aug 2022	none	MIT	—	Details →
2.0.0-beta0	05 Aug 2022	none	MIT	—	Details →
2.0.0-alpha7	17 Mar 2022	none	MIT	—	Details →
1.7.36	08 Feb 2022	none	MIT	—	Details →
1.7.35	25 Jan 2022	none	MIT	—	Details →
1.7.34	25 Jan 2022	none	MIT	—	Details →
2.0.0-alpha6	13 Jan 2022	none	MIT	—	Details →
1.7.33	13 Jan 2022	none	MIT	—	Details →
2.0.0-alpha5	30 Aug 2021	none	MIT	—	Details →
2.0.0-alpha4	12 Aug 2021	none	MIT	—	Details →
2.0.0-alpha3	10 Aug 2021	none	MIT	—	Details →
1.7.32	20 Jul 2021	none	MIT	—	Details →
2.0.0-alpha2	02 Jul 2021	none	MIT	—	Details →
1.7.31	17 Jun 2021	none	MIT	—	Details →
1.7.30	16 Dec 2019	none	MIT	—	Details →
1.7.29	31 Oct 2019	none	MIT	—	Details →
2.0.0-alpha1	01 Oct 2019	none	MIT	—	Details →
1.7.28	10 Aug 2019	none	MIT	—	Details →
1.7.27	06 Aug 2019	none	MIT	—	Details →
2.0.0-alpha0	12 Jun 2019	none	MIT	—	Details →
1.8.0-beta4	19 Feb 2019	none	MIT	—	Details →
1.7.26	18 Feb 2019	none	MIT	—	Details →
1.8.0-beta2	21 Mar 2018	none	MIT	—	Details →
1.8.0-beta1	30 Jan 2018	none	MIT	—	Details →
1.8.0-beta0	20 Oct 2017	none	MIT	—	Details →
1.8.0-alpha2	25 Apr 2017	none	MIT	—	Details →
1.8.0-alpha1	13 Apr 2017	none	MIT	—	Details →
1.8.0-alpha0	07 Apr 2017	none	MIT	—	Details →
1.7.25	16 Mar 2017	none	MIT	—	Details →
1.7.24	24 Feb 2017	none	MIT	—	Details →
1.7.23	14 Feb 2017	none	MIT	—	Details →
1.7.22	13 Dec 2016	none	MIT	—	Details →
1.7.21	04 Apr 2016	none	MIT	—	Details →
1.7.20	29 Mar 2016	none	MIT	—	Details →
1.7.19	14 Mar 2016	none	MIT	—	Details →
1.7.18	26 Feb 2016	none	MIT	—	Details →
1.7.16	11 Feb 2016	none	MIT	—	Details →
1.7.15	09 Feb 2016	none	MIT	—	Details →
1.7.14	24 Jan 2016	none	MIT	—	Details →
1.7.13	10 Nov 2015	none	MIT	—	Details →
1.7.12	26 Mar 2015	none	MIT	—	Details →
1.7.11	26 Mar 2015	none	MIT	—	Details →
1.7.10	06 Jan 2015	none	MIT	—	Details →
1.7.9	16 Dec 2014	none	MIT	—	Details →
1.7.8	14 Dec 2014	none	MIT	—	Details →
1.7.7	04 Apr 2014	none	MIT	—	Details →
1.7.6	05 Feb 2014	none	MIT	—	Details →
1.7.5	25 Mar 2013	none	MIT	—	Details →
1.7.4	18 Mar 2013	none	MIT	—	Details →
1.7.3	15 Mar 2013	none	MIT	—	Details →
1.7.2	11 Oct 2012	none	MIT	—	Details →
1.7.1	14 Sep 2012	none	MIT	—	Details →
1.7.0	06 Sep 2012	none	MIT	—	Details →
1.6.6	11 Jun 2012	none	MIT	—	Details →
1.6.5	04 Jun 2012	none	MIT	—	Details →
1.6.4	31 Oct 2011	none	MIT	—	Details →
1.6.3	17 Oct 2011	none	MIT	—	Details →
1.6.2	18 Aug 2011	none	MIT	—	Details →
1.6.1	05 Jul 2010	none	MIT	—	Details →
1.6.0	08 May 2010	none	MIT	—	Details →
1.6.0-alpha2	26 Apr 2010	none	MIT	—	Details →
1.6.0-RC0	21 Apr 2010	none	MIT	—	Details →
1.5.11	25 Feb 2010	none	MIT	—	Details →
1.5.10	02 Dec 2009	none	MIT	—	Details →
1.5.9.RC1	29 Oct 2009	none	MIT	—	Details →
1.5.9-RC0	04 Sep 2009	none	MIT	—	Details →
1.5.8	11 Jun 2009	none	—	—	Details →
1.5.7	10 Jun 2009	none	—	—	Details →
1.5.6	21 Nov 2008	none	—	—	Details →
1.5.5	17 Oct 2008	none	—	—	Details →
1.5.4	16 Oct 2008	none	—	—	Details →
1.5.3	12 Sep 2008	none	—	—	Details →
1.5.2	09 Jun 2008	none	—	—	Details →
1.5.0	26 Feb 2008	none	—	—	Details →
1.5.0-M0	29 Jan 2008	none	—	—	Details →
1.4.3	20 Aug 2007	none	—	—	Details →
1.4.2	12 Jul 2007	none	—	—	Details →
1.4.1	04 Jul 2007	none	—	—	Details →
1.4.0	22 May 2007	none	—	—	Details →
1.3.1	15 Apr 2007	none	—	—	Details →
1.3.0	25 Feb 2007	none	—	—	Details →
1.2	24 Jan 2007	none	—	—	Details →
1.1.0	20 Dec 2006	none	—	—	Details →
1.1.0-RC1	16 Nov 2006	none	—	—	Details →
1.1.0-RC0	09 Nov 2006	none	—	—	Details →
1.1.0-beta0	17 Sep 2006	none	—	—	Details →

All 109 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for org.slf4j:slf4j-api

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.slf4j:slf4j-api

Is org.slf4j:slf4j-api safe to use?

Vulert has no vulnerabilities on record for org.slf4j:slf4j-api 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.slf4j:slf4j-api's Vulert package health score?

Vulert scores org.slf4j:slf4j-api 71/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.slf4j:slf4j-api affected?

No. 2.1.0-alpha1, 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.slf4j:slf4j-api should I use?

2.1.0-alpha1 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.slf4j:slf4j-api have?

0 vulnerabilities are recorded for org.slf4j:slf4j-api 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.slf4j:slf4j-api vulnerabilities disclosed?

0 vulnerabilities were recorded for org.slf4j:slf4j-api 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.slf4j:slf4j-api 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.slf4j:slf4j-api for upcoming vulnerabilities?

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