VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

frigate: vulnerability history, versions and safety

frigate is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 29 releases, from May 2024 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 H1 U2
i
1 with no fix published

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

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all frigate vulnerabilities

Vulert verdict on frigate 0.7.0 i

Updated on 23 Oct 2026

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

Package health score 51/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Not enough data

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 0.7.0 — affected i
  • Vulnerabilities on record 4 over 2 years · 3 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 1 i
  • Last release 42 months ago i
  • Licence Apache-2.0 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 frigate, 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
0.8.0a0.post0.dev41 10 Dec 2024 H1 U2 Apache-2.0 No Details →
0.8.0a0.post0.dev40 18 Oct 2023 C1 H1 U2 Apache-2.0 No Details →
0.8.0a0.post0.dev39 28 Apr 2023 C1 H1 U2 Apache-2.0 No Details →
0.7.0 31 Mar 2023 C1 H1 U2 Apache-2.0 No Details →
0.7.0a0.post0.dev38 30 Mar 2023 C1 H1 U2 Apache-2.0 No Details →
0.7.0a0.post0.dev37 10 Mar 2023 C1 H1 U2 Apache-2.0 No Details →
0.7.0a0.post0.dev34 09 Mar 2023 C1 H1 U2 Apache-2.0 No Details →
0.7.0a0.post0.dev32 09 Mar 2023 C1 H1 U2 Apache-2.0 No Details →
0.7.0a0.post0.dev1 01 Aug 2022 C1 H1 U2 Apache-2.0 No Details →
0.6.1 19 Jul 2022 C1 H1 U2 Apache-2.0 No Details →
0.7.0a0 30 Jun 2022 C1 H1 U2 Apache-2.0 No Details →
0.6.0a0.post0.dev4 30 Jun 2022 C1 H1 U2 Apache-2.0 No Details →
0.6.0 29 Jun 2022 C1 H1 U2 Apache-2.0 No Details →
0.6.0a0.post0.dev3 28 Jun 2022 C1 H1 U2 Apache-2.0 No Details →
0.6.0a0.post0.dev2 07 Jun 2022 C1 H1 U2 Apache-2.0 No Details →
0.6.0a0 09 Feb 2022 C1 H1 U2 Apache-2.0 No Details →
0.5.0a0.post0.dev8 09 Feb 2022 C1 H1 U2 Apache-2.0 No Details →
0.5.0 09 Feb 2022 C1 H1 U2 Apache-2.0 No Details →
0.5.0a0.post0.dev7 09 Feb 2022 C1 H1 U2 Apache-2.0 No Details →
0.5.0a0.post0.dev4 02 Feb 2022 C1 H1 U2 Apache-2.0 No Details →
0.5.0a0.post0.dev3 26 Aug 2021 C1 H1 U2 Apache-2.0 No Details →
0.5.0a0.post0.dev2 23 Aug 2021 C1 H1 U2 Apache-2.0 No Details →
0.5.0a0 01 Jul 2021 C1 H1 U2 Apache-2.0 No Details →
0.4.0 01 Jul 2021 C1 H1 U2 Apache-2.0 No Details →
0.4.0a0.post0.dev14 30 Jun 2021 C1 H1 U2 Apache-2.0 No Details →
0.4.0a0 27 Apr 2021 C1 H1 U2 Apache-2.0 No Details →
0.3.0 31 Mar 2021 C1 H1 U2 Apache-2.0 No Details →
0.2.0 28 May 2020 C1 H1 U2 Apache-2.0 No Details →
0.1.0 29 Apr 2020 C1 H1 U2 Apache-2.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for frigate

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Multiple Application-level Denial of Service in Frigate 9.3 critical 0.13.2 09 May 2024
CVE-2024-32874: Frigate Package Vulnerability Leading to Application-level Denial of Service via Malicious Unicode Filenames 9.3 critical 0.13.2 29 Jun 2026
CVE-2026-33125: Frigate Package Allows Viewer Role to Delete Admin Accounts 7.1 high No fix published 18 Mar 2026
CVE-2026-33125: Frigate Package Allows Viewer Role to Delete Admin Accounts 7.1 high 0.16.3 13 Jul 2026

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 frigate

Is frigate safe to use?

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

What is frigate's Vulert package health score?

Vulert scores frigate 51/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 frigate affected?

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

How many vulnerabilities does frigate have?

4 vulnerabilities are recorded for frigate in the PyPI ecosystem: 1 critical, 1 high, 0 medium and 0 low, plus 2 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 frigate vulnerabilities disclosed?

3 vulnerabilities were recorded for frigate in the last 12 months, and the oldest entry in this database dates to 09 May 2024. 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 frigate 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 frigate for upcoming vulnerabilities?

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