# CVE-2020-37049: Frigate 3.36.0.9 - 'Command Line' Local Buffer Overflow

> A local buffer overflow in Frigate Professional allows attackers to execute arbitrary code via crafted command line input.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jan 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-m38g-q284-wqcq

## What is CVE-2020-37049?

CVE-2020-37049 is a high-severity memory corruption vulnerability in WinFrigate Frigate 3 Professional, published on 30 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Frigate 3.36.0.9 contains a local buffer overflow vulnerability in the Command Line input field that allows attackers to execute arbitrary code. Attackers can craft a malicious payload to overflow the buffer, bypass DEP, and execute commands like launching calc.exe through a specially crafted input sequence.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2020-37049?


## How do I fix CVE-2020-37049?

No fix has been published for CVE-2020-37049 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-37049 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37049 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37049 and fix it if it is affected.

What it is: CVE-2020-37049 is a high-severity memory corruption vulnerability in WinFrigate Frigate 3 Professional, published on 30 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37049 exists.

Affected product: WinFrigate Frigate 3 Professional. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-37049/ (Markdown: https://insights.sbomify.com/CVE-2020-37049/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-37049
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-37049
- OSV: https://osv.dev/vulnerability/CVE-2020-37049

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-37049/
Summaries are generated and may contain mistakes; the official description above is the record.