VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.sun.faces:jsf-api: vulnerability history, versions and safety

com.sun.faces:jsf-api is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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 com.sun.faces:jsf-api vulnerabilities

Vulert verdict on com.sun.faces:jsf-api 2.2.20 i

Updated on 23 Oct 2026

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

Package health score 74/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Not enough data

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

  • Current release 2.2.20 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 01 May 2022 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 20 packages i
  • Last release 86 months ago i
  • Licence non-standard 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 com.sun.faces:jsf-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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.2.8-35 17 Oct 2019 none non-standard — Details →
2.2.20 31 Jul 2019 none non-standard — Details →
2.2.8-34 31 Jul 2019 none non-standard — Details →
2.2.8-33 12 Jul 2019 none non-standard — Details →
2.2.19 25 Apr 2019 none non-standard — Details →
2.2.8-32 02 Apr 2019 none non-standard — Details →
2.2.8-31 16 Nov 2018 none non-standard — Details →
2.2.8-30 04 Sep 2018 none non-standard — Details →
2.1.29-11 04 Sep 2018 none non-standard — Details →
2.2.18 22 Aug 2018 none non-standard — Details →
2.2.8-29 25 Jul 2018 none non-standard — Details →
2.2.8-28 21 Jun 2018 none non-standard — Details →
2.1.7-10 12 May 2018 none non-standard — Details →
2.0.9-08 12 May 2018 none non-standard — Details →
2.0.4-b16 13 Apr 2018 none non-standard — Details →
2.1.29-10 12 Apr 2018 none non-standard — Details →
2.2.17 12 Apr 2018 none non-standard — Details →
2.1.20-16 09 Apr 2018 none non-standard — Details →
2.2.8-27 08 Apr 2018 none non-standard — Details →
2.2.16 18 Jan 2018 none non-standard — Details →
2.2.8-26 13 Dec 2017 none non-standard — Details →
2.2.8-25 27 Nov 2017 none non-standard — Details →
2.2.15 10 Oct 2017 none non-standard — Details →
2.2.8-24 19 Sep 2017 none non-standard — Details →
2.2.8-23 16 Jun 2017 none non-standard — Details →
2.2.8-22 02 Jun 2017 none non-standard — Details →
2.2.8-21 11 Apr 2017 none non-standard — Details →
2.2.8-20 10 Apr 2017 none non-standard — Details →
2.1.20-15 08 Mar 2017 none non-standard — Details →
2.1.7-09 08 Mar 2017 none non-standard — Details →
2.2.8-19 07 Feb 2017 none non-standard — Details →
2.2.14 15 Nov 2016 none non-standard — Details →
2.1.20-14 26 Aug 2016 none non-standard — Details →
2.2.8-18 18 Aug 2016 none non-standard — Details →
2.2.8-17 04 Aug 2016 none non-standard — Details →
2.0.4-b15 15 Jul 2016 none non-standard — Details →
2.1.29-08 14 Jul 2016 none non-standard — Details →
2.0.11-04 14 Jul 2016 none non-standard — Details →
2.0.4-b14 13 Jul 2016 none non-standard — Details →
2.1.20-13 07 Jul 2016 none non-standard — Details →
2.0.9-06 06 Jul 2016 none non-standard — Details →
2.1.7-08 06 Jul 2016 none non-standard — Details →
2.1.20-12 31 May 2016 none non-standard — Details →
2.2.8-16 30 May 2016 none non-standard — Details →
2.1.29-07 26 May 2016 none non-standard — Details →
2.0.11-03 24 May 2016 none non-standard — Details →
2.1.29-06 18 May 2016 none non-standard — Details →
2.1.20-11 07 May 2016 none non-standard — Details →
2.1.20-10 19 Apr 2016 none non-standard — Details →
2.0.9-05 19 Apr 2016 none non-standard — Details →
2.2.8-15 15 Apr 2016 none non-standard — Details →
2.0.4-b13 14 Apr 2016 none non-standard — Details →
2.1.7-07 13 Apr 2016 none non-standard — Details →
2.2.8-14 01 Apr 2016 none non-standard — Details →
2.2.8-13 09 Mar 2016 none non-standard — Details →
2.1.20-09 23 Feb 2016 none non-standard — Details →
2.2.13 04 Feb 2016 none non-standard — Details →
2.1.29-05 20 Jan 2016 none non-standard — Details →
2.2.8-12 04 Jan 2016 none non-standard — Details →
2.1.20-08 28 Oct 2015 none non-standard — Details →
2.0.9-04 10 Aug 2015 none non-standard — Details →
2.1.7-06 07 Aug 2015 none non-standard — Details →
2.1.29-04 30 Jul 2015 none non-standard — Details →
2.2.12 20 Jul 2015 none non-standard — Details →
2.2.8-11 17 Jul 2015 none non-standard — Details →
2.2.8-10 25 Jun 2015 none non-standard — Details →
2.2.8-09 11 Jun 2015 none non-standard — Details →
2.2.8-08 26 May 2015 none non-standard — Details →
2.0.9-03 19 May 2015 none non-standard — Details →
2.1.5-04 18 May 2015 none non-standard — Details →
2.1.7-05 17 May 2015 none non-standard — Details →
2.1.20-07 17 May 2015 none non-standard — Details →
2.0.4-13 16 May 2015 none non-standard — Details →
2.0.11-02 15 May 2015 none non-standard — Details →
2.1.29-03 14 May 2015 none non-standard — Details →
2.1.20-06 07 May 2015 none non-standard — Details →
2.1.7-04 07 May 2015 none non-standard — Details →
2.1.29-02 07 May 2015 none non-standard — Details →
2.2.11 05 May 2015 none non-standard — Details →
2.2.8-07 04 May 2015 none non-standard — Details →
2.1.20-05 09 Feb 2015 none non-standard — Details →
2.2.10 05 Feb 2015 none non-standard — Details →
2.2.8-06 04 Feb 2015 none non-standard — Details →
2.1.29-01 30 Jan 2015 none non-standard — Details →
2.2.8-05 22 Jan 2015 none non-standard — Details →
2.2.9 18 Dec 2014 none non-standard — Details →
2.2.8-04 09 Dec 2014 none non-standard — Details →
2.2.8-02 15 Sep 2014 none non-standard — Details →
2.2.8-01 27 Aug 2014 none non-standard — Details →
2.2.8 14 Aug 2014 none non-standard — Details →
2.1.5-03 09 Jul 2014 none non-standard — Details →
2.1.29 02 Jul 2014 none non-standard — Details →
2.2.7 10 Jun 2014 none non-standard — Details →
2.0.11-01 14 May 2014 none non-standard — Details →
2.0.9-02 11 Mar 2014 none non-standard — Details →
2.0.4-12 11 Mar 2014 none non-standard — Details →
2.2.6 04 Mar 2014 none non-standard — Details →
2.1.28 03 Mar 2014 none non-standard — Details →
2.1.5-02 03 Mar 2014 none non-standard — Details →
2.1.20-04 28 Feb 2014 none non-standard — Details →
2.1.7-03 28 Feb 2014 none — — Details →
2.1.27 08 Jan 2014 none — — Details →
2.2.5 08 Jan 2014 none — — Details →
2.2.4 03 Oct 2013 none — — Details →
2.2.3 05 Sep 2013 none — — Details →
2.1.26 05 Sep 2013 none — — Details →
2.2.2 09 Aug 2013 none — — Details →
2.1.25 08 Aug 2013 none — — Details →
2.1.7-02 25 Jul 2013 none — — Details →
2.0.4-b12 25 Jul 2013 none — — Details →
2.2.1 09 Jul 2013 none — — Details →
2.1.24 09 Jul 2013 none — — Details →
2.1.23 13 Jun 2013 none — — Details →
2.1.22 08 May 2013 none — — Details →
2.2.0 02 May 2013 none — — Details →
2.2.0-m15 26 Apr 2013 none — — Details →
2.2.0-m14 12 Apr 2013 none — — Details →
2.1.21 09 Apr 2013 none — — Details →
2.2.0-m13 02 Apr 2013 none — — Details →
2.1.7-01 27 Mar 2013 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for com.sun.faces:jsf-api

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2008-1285: Cross-site scripting (XSS) vulnerability in Sun Java Server Faces (JSF) 5.3 medium 1.2.08 01 May 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 com.sun.faces:jsf-api

Is com.sun.faces:jsf-api safe to use?

Vulert records 1 vulnerabilities for com.sun.faces:jsf-api in Maven: 0 critical, 0 high, 1 medium and 0 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 com.sun.faces:jsf-api's Vulert package health score?

Vulert scores com.sun.faces:jsf-api 74/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 com.sun.faces:jsf-api affected?

No. 2.2.20, 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 com.sun.faces:jsf-api should I use?

2.2.20 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 com.sun.faces:jsf-api have?

1 vulnerability is recorded for com.sun.faces:jsf-api in the Maven ecosystem: 0 critical, 0 high, 1 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 com.sun.faces:jsf-api vulnerabilities disclosed?

0 vulnerabilities were recorded for com.sun.faces:jsf-api in the last 12 months, and the oldest entry in this database dates to 01 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 com.sun.faces:jsf-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 com.sun.faces:jsf-api for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the com.sun.faces:jsf-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.