VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

fava: vulnerability history, versions and safety

fava is a package in the PyPI ecosystem. Vulert records 7 vulnerabilities for it across 61 releases, from Jul 2022 to Aug 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded M3 U4
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 fava vulnerabilities

Vulert verdict on fava 1.30.16 i

Updated on 23 Oct 2026

Careful: 1.30.16 has 2 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.30.16 — affected i
  • Vulnerabilities on record 7 over 1 year · 0 in the last year i
  • Latest disclosure 02 Aug 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 1 i
  • Depended on by 16 packages i
  • Stars 2,593 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, 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 fava, 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
1.30.16 18 Aug 2026 U2 MIT No Details →
1.30.15 15 Aug 2026 U2 MIT No Details →
1.30.14 16 Jun 2026 U2 MIT No Details →
1.30.13 19 May 2026 U2 MIT No Details →
1.30.12 17 Feb 2026 U2 MIT No Details →
1.30.11 17 Jan 2026 U2 MIT No Details →
1.30.10 12 Jan 2026 U2 MIT No Details →
1.30.9 02 Jan 2026 U2 MIT No Details →
1.30.8 13 Dec 2025 U2 MIT No Details →
1.30.7 12 Oct 2025 U2 MIT No Details →
1.30.6 16 Sep 2025 U2 MIT No Details →
1.30.5 16 Jul 2025 U2 MIT No Details →
1.30.4 02 Jul 2025 U2 MIT No Details →
1.30.3 20 May 2025 U2 MIT No Details →
1.30.2 25 Mar 2025 U2 MIT No Details →
1.30.1 08 Feb 2025 U2 MIT No Details →
1.30.0 29 Dec 2024 U2 MIT No Details →
1.29.0 09 Oct 2024 U2 MIT No Details →
1.28.0 07 Jul 2024 U2 MIT No Details →
1.27.3 11 Mar 2024 U2 MIT No Details →
1.27.2 05 Feb 2024 U2 MIT No Details →
1.27.1 19 Jan 2024 U2 MIT No Details →
1.27.0 06 Jan 2024 U2 MIT No Details →
1.26.4 30 Dec 2023 U2 MIT No Details →
1.26.3 24 Dec 2023 U2 MIT No Details →
1.26.2 25 Oct 2023 U2 MIT No Details →
1.26.1 23 Sep 2023 U2 MIT No Details →
1.26.0 04 Sep 2023 U2 MIT No Details →
1.25.1 02 Aug 2023 U2 MIT No Details →
1.25.0 17 Jul 2023 U2 MIT No Details →
1.24.4 07 Apr 2023 U2 MIT No Details →
1.24.3 01 Apr 2023 U2 MIT No Details →
1.24.2 01 Apr 2023 U2 MIT No Details →
1.24.1 26 Mar 2023 U2 MIT No Details →
1.24.0 21 Feb 2023 U2 MIT No Details →
1.23.1 30 Oct 2022 U2 MIT No Details →
1.23.0 15 Oct 2022 U2 MIT No Details →
1.22.3 30 Jul 2022 U2 MIT No Details →
1.22.2 23 Jul 2022 M1 U1 MIT Yes Details →
1.22.1 13 Jul 2022 M2 U2 MIT Yes Details →
1.22.0 03 Jul 2022 M2 U2 MIT No Details →
1.21.0 06 Feb 2022 M3 U2 MIT No Details →
1.20.1 22 Sep 2021 M3 U3 MIT Yes Details →
1.20.0 19 Sep 2021 M3 U2 MIT No Details →
1.19.0 18 May 2021 M3 U2 MIT No Details →
1.18.0 16 Jan 2021 M3 U2 MIT No Details →
1.17.0 15 Nov 2020 M3 U2 MIT No Details →
1.16.0 18 Oct 2020 M3 U2 MIT No Details →
1.15.0 30 May 2020 M3 U2 MIT No Details →
1.14.0 16 Feb 2020 M3 U2 MIT No Details →
1.13.0 01 Feb 2020 M3 U2 MIT No Details →
1.12.0 03 Dec 2019 M3 U2 MIT No Details →
1.11.0 20 Aug 2019 M3 U2 MIT No Details →
1.10.0 31 Jan 2019 M3 U2 MIT No Details →
1.9.0 08 Oct 2018 M3 U2 MIT No Details →
1.8.0 25 Jul 2018 M3 U2 MIT No Details →
1.7.0 09 Mar 2018 M3 U2 MIT No Details →
1.6.0 07 Nov 2017 M3 U2 MIT No Details →
1.5.0 23 Jul 2017 M3 U2 MIT No Details →
1.4.0 15 May 2017 M3 U2 MIT No Details →
1.3.0 15 Mar 2017 M3 U2 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 7

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

03 Vulnerabilities

Recorded vulnerabilities for fava

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-2523: Fava Reflected Cross-site Scripting Vulnerability 6.1 medium 1.22.2 26 Jul 2022
CVE-2022-2514: Fava time and filter parameters vulnerable to reflected XSS before v1.22 6.1 medium 1.22 26 Jul 2022
CVE-2022-2589: Reflected Cross-Site Scripting in Fava 6.1 medium 1.22.3 02 Aug 2022
CVE-2022-2514: Fava Reflected XSS Vulnerability Due to Lack of Escaping 6.1 medium No fix published 25 Jul 2022
CVE-2022-2514: Reflected XSS in fava N/A unrated ca9e3882c7b5fbf5273ba52340b9fea6a99f3711 25 Jul 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 fava

Is fava safe to use?

Vulert records 7 vulnerabilities for fava in PyPI: 0 critical, 0 high, 3 medium and 0 low, plus 4 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is fava's Vulert package health score?

Vulert scores fava 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of fava affected?

Yes. 1.30.16, the version you would install today, has 2 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of fava should I use?

1.30.16 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 fava have?

7 vulnerabilities are recorded for fava in the PyPI ecosystem: 0 critical, 0 high, 3 medium and 0 low, plus 4 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new fava vulnerabilities disclosed?

0 vulnerabilities were recorded for fava in the last 12 months, and the oldest entry in this database dates to 25 Jul 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 fava 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 fava for upcoming vulnerabilities?

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