KEVWire

Security intelligence, with context.

Response snapshot Oct 27, 2026, 17:26 UTC

Back to the wire
Permalink
VulnerabilityCVE-2024-32874

Malicious Long Unicode filenames may cause a Multiple Application-level Denial of Service

**Important: Exploiting this vulnerability requires the attacker to have access to your Frigate instance, which means they could also just delete all of your recordings or perform any other action.

At a glance

Exploited
Not known
Severity
9.3 Critical (CVSS 3.1)
Chance of exploitation
Not estimated
Sources
1 source

What to do

GitHub lists first patched versions: frigate: 0.13.2. Confirm the affected range and upgrade guidance in the exact advisory.

Read GitHub-reviewed advisory GHSA-w4h6-9wrp-v5jq (opens a new tab)

What happened

**Important: Exploiting this vulnerability requires the attacker to have access to your Frigate instance, which means they could also just delete all of your recordings or perform any other action. If you have configured authentication in front of Frigate via a reverse proxy, then this vulnerability is not exploitable without first getting around your authentication method.

For many obvious reasons in addition to this one, please don't expose your Frigate instance publicly without any kind of authentication.**

## Summary

When uploading a file or retrieving the filename, a user may intentionally use a large Unicode filename which would lead to a application-level denial of service. This is due to no limitation set on the length of the filename and the costy use of the Unicode normalization with the form NFKD under the hood of `secure_filename()`.

Continue reading

I idenfied multiple vulnerable paths on [blakeblackshear/frigate](https://www.github.com/blakeblackshear/frigate/) repository.

In all of those paths, it was possible for a malicious user to send a filename equals to the output of : `python3 -c "print('℀' * 1_000_000)"` which would reach the werkzeug `secure_filename()` call , which in turn under the hood uses a compatibility Unicode normalization with NFKC/NFKD form. In sum, the latter call would be costly in matter of CPU resource and may lead to the application-level denial of service.

## Vulnerable Paths

Path with 2 steps

1. [frigate/api/media.py](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L379C20-L379C31) @MediaBp.route("/<camera_name>/start/<int:start_ts>/end/<int:end_ts>/clip.mp4") @MediaBp.route("/<camera_name>/start/<float:start_ts>/end/<float:end_ts>/clip.mp4") def recording_clip( camera_name , start_ts, end_ts): download = request.args.get("download", type=bool)

2. [frigate/api/media.py](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L408C33-L408C78) playlist_lines.append(f"outpoint {int(end_ts - clip.start_time)}")

file_name = secure_filename( f"clip_{camera_name}_{start_ts}-{end_ts}.mp4" ) path = os.path.join(CACHE_DIR, file_name)

----------------------------------------

[frigate/api/media.py](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L408C33-L408C78)

playlist_lines.append(f"outpoint {int(end_ts - clip.start_time)}")

file_name = secure_filename( f"clip_{camera_name}_{start_ts}-{end_ts}.mp4" ) path = os.path.join(CACHE_DIR, file_name)

*This [user-provided value](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L379C33-L379C41) can reach a [costly Unicode normalization operation](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L408C33-L408C78).*

#### Paths

Path with 2 steps

1. [frigate/api/media.py](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L379C33-L379C41) @MediaBp.route("/<camera_name>/start/<int:start_ts>/end/<int:end_ts>/clip.mp4") @MediaBp.route("/<camera_name>/start/<float:start_ts>/end/<float:end_ts>/clip.mp4") def recording_clip(camera_name, start_ts , end_ts): download = request.args.get("download", type=bool)

2. [frigate/api/media.py](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L408C33-L408C78) playlist_lines.append(f"outpoint {int(end_ts - clip.start_time)}")

file_name = secure_filename( f"clip_{camera_name}_{start_ts}-{end_ts}.mp4" ) path = os.path.join(CACHE_DIR, file_name)

----------------------------------------

[frigate/api/media.py](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L408C33-L408C78)

playlist_lines.append(f"outpoint {int(end_ts - clip.start_time)}")

file_name = secure_filename( f"clip_{camera_name}_{start_ts}-{end_ts}.mp4" ) path = os.path.join(CACHE_DIR, file_name)

*This [user-provided value](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L379C43-L379C49) can reach a [costly Unicode normalization operation](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L408C33-L408C78).*

#### Paths

Path with 2 steps

1. [frigate/api/media.py](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L379C43-L379C49) @MediaBp.route("/<camera_name>/start/<int:start_ts>/end/<int:end_ts>/clip.mp4") @MediaBp.route("/<camera_name>/start/<float:start_ts>/end/<float:end_ts>/clip.mp4") def recording_clip(camera_name, start_ts, end_ts ): download = request.args.get("download", type=bool)

2. [frigate/api/media.py](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L408C33-L408C78) playlist_lines.append(f"outpoint {int(end_ts - clip.start_time)}")

file_name = secure_filename( f"clip_{camera_name}_{start_ts}-{end_ts}.mp4" ) path = os.path.join(CACHE_DIR, file_name)

----------------------------------------

[frigate/api/media.py](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L646C25-L646C47)

current_app.frigate_config, camera_name, secure_filename( name.replace(" ", "_") ) if name else None, int(start_time), int(end_time),

*This [user-provided value](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L23C5-L23C12) can reach a [costly Unicode normalization operation](https://github.com/blakeblackshear/frigate/blob/d7ae0eedf89e14f297093ac5c8042862034cbaeb/frigate/api/media.py#L646C25-L646C47).*

#### Paths

Path with 8 steps

1. [frigate/api/media.py](https:

Affected package ranges reported by GitHub: frigate: < 0.13.2

Scores and how they were measured

CVSS base severity

9.3

Version 3.1As of

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

Measurement source (opens a new tab)

How bad it is if exploited. Not a prediction of exploitation or proof you are exposed.

EPSS probability

Not available

A model's estimate of exploitation in the next 30 days, not certainty or your own risk.

Related technology

Sources

  1. Primary source

    GitHub-reviewed advisory GHSA-w4h6-9wrp-v5jq (opens a new tab)

    The public advisory supplies the description, affected package/version ranges, and any listed CVSS metric. GitHub review is not local review.

    Published Checked

  2. Primary source

    GitHub public advisory API page (opens a new tab)

    The API page supplied GHSA-w4h6-9wrp-v5jq, its actual identifiers, source dates, and structured metrics.

    Published Date not suppliedChecked

Cite this record

For factual claims, cite the primary sources above; cite KEVWire for its compilation, dates, and classifications.

APA

KEVWire. (2026, October 27). Malicious Long Unicode filenames may cause a Multiple Application-level Denial of Service (CVE-2024-32874). https://kevwire.com/record/CVE-2024-32874

MLA

"Malicious Long Unicode filenames may cause a Multiple Application-level Denial of Service (CVE-2024-32874)." KEVWire, 27 Oct. 2026, kevwire.com/record/CVE-2024-32874.

Chicago

KEVWire. "Malicious Long Unicode filenames may cause a Multiple Application-level Denial of Service (CVE-2024-32874)." Last modified October 27, 2026. https://kevwire.com/record/CVE-2024-32874.

Evidence summary (plain text)

Malicious Long Unicode filenames may cause a Multiple Application-level Denial of Service (May 9, 2024).
**Important: Exploiting this vulnerability requires the attacker to have access to your Frigate instance, which means they could also just delete all of your recordings or perform any other action. If you have configured authentication in front of Frigate via a reverse proxy, then this vulnerability is not exploitable without first getting around your authentication method. For many obvious reasons in addition to this one, please don't expose your Frigate instance publicly without any kind of authentication.**

When uploading a file or retrieving the filename, a user may intentionally use a large Unicode filename which would lead to a application-level denial of service. This is due to no limitation set on the length of the filename and the costy use of the Unicode normalization with the form NFKD under the hood of `secure_filename()`.
CVSS 9.3 (version 3.1; evidence as of Oct 27, 2026; https://github.com/advisories/GHSA-w4h6-9wrp-v5jq).
Sources:
GitHub-reviewed advisory GHSA-w4h6-9wrp-v5jq: https://github.com/advisories/GHSA-w4h6-9wrp-v5jq
GitHub public advisory API page: https://api.github.com/advisories?type=reviewed&per_page=100&sort=updated&direction=desc
Record ID: CVE-2024-32874.
Record origin: Ingested record.
AI evidence: Not assessed.
Known exploitation: Not assessed.
Zero-day status: Not assessed. KEV membership alone does not establish zero-day status.
About this data

This record was ingested from a data source. Retrieved: Oct 27, 2026, 17:25 UTC. Ingestion is not an independent editorial investigation.

A CISA KEV listing documents known exploitation, not necessarily a zero-day; absence from the catalog does not prove a vulnerability has never been exploited.

Technology tags indicate possible relevance, not verified exposure. Confirm the affected product, version, and configuration against your own inventory; KEVWire does not scan your systems.

A personal reading checklist on this device, not verified remediation.

Record JSON

Your account

Email alerts

Email alerts are not available yet. To follow your stack today, use its RSS feed, which honors your filters, or connect an AI agent through the API.

Suggest an improvement

Ideas, missing sources, corrections, and bugs are all welcome. No account needed. Suggestions are reviewed by a person before anything changes.

Record details

Record detail