VulnerabilityPublished 9 May 2024Updated 27 Oct 2026

CVE-2024-32874: Frigate · Malicious Long Unicode filenames may cause a Multiple Application-level Denial of Service

Affects frigateSource GCVE Database

Not known to be exploited · CVSS 9.3 Critical : upgrade to 0.13.2 as a priority.

Data as of 27 Oct 2026, 17:29 UTC

CVSS 3.1 base score

9.3Critical

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 0.13.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade frigate to 0.13.2.

Affected software

Product	Affected	Fixed in
PyPIfrigate	Affected <0.13.2	Fixed in 0.13.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Frigate version 0.13.2 that addresses this vulnerability. Users should upgrade to version 0.13.2 or later. Additionally, ensure that authentication is configured in front of the Frigate instance (e.g., via a reverse proxy) to prevent unauthorized access, as exploitation requires access to the instance. Do not expose the Frigate instance publicly without authentication.

Description

CVE-2024-32874 is a critical application-level denial of service vulnerability in Frigate versions prior to 0.13.2. It arises when an attacker with access to the Frigate instance uploads or uses extremely long Unicode filenames, which trigger costly Unicode normalization operations in the secure_filename() function. This can exhaust CPU resources and cause the application to become unresponsive. Exploitation requires attacker access to the Frigate instance, and proper authentication can prevent exploitation. A fix is available in version 0.13.2.

Impact

Successful exploitation results in an application-level denial of service by exhausting CPU resources during filename normalization. The attacker must have access to the Frigate instance, which implies they could perform other malicious actions such as deleting recordings. There is no direct confidentiality impact, but integrity is partially affected since the attacker can disrupt service and potentially interfere with recordings. Availability is significantly impacted due to the denial of service condition.

Summary

This vulnerability involves the handling of user-supplied filenames in the Frigate application. Specifically, when a filename containing a very large number of repeated Unicode characters is processed, the secure_filename() function performs Unicode normalization using the NFKD form, which is computationally expensive. An attacker can exploit this by submitting filenames such as a string of 1,000,000 '℀' characters, causing excessive CPU consumption and leading to an application-level denial of service. The vulnerable code paths are in the media API endpoints where filenames are constructed from user-controlled camera_name parameters and timestamps. The vulnerability requires attacker access to the Frigate instance, and is mitigated if authentication is properly configured. The issue is fixed in Frigate version 0.13.2.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 17:29 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats