# CVE-2025-57440: Missing authorization in n/a

> An undocumented Telnet service allows unauthenticated attackers to execute arbitrary commands, erase disks, or reboot the device.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-cgfc-2m55-wph7

## What is CVE-2025-57440?

CVE-2025-57440 is a high-severity missing authorization vulnerability in n/a, published on 22 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Blackmagic ATEM Mini Pro 2.7 exposes an undocumented Telnet service on TCP port 9993, which accepts unauthenticated plaintext commands for controlling streaming, recording, formatting storage devices, and system reboot. This interface, referred to as the "ATEM Ethernet Protocol 1.0", provides complete device control without requiring credentials or encryption. An attacker on the same network (or with remote access to the exposed port) can exploit this interface to execute arbitrary streaming commands, erase disks, or shut down the device - effectively gaining full remote control.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-57440?


## How do I fix CVE-2025-57440?

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

## Is CVE-2025-57440 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57440 and fix it if it is affected.

What it is: CVE-2025-57440 is a high-severity missing authorization vulnerability in n/a, published on 22 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57440 exists.

Affected product: n/a. 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-2025-57440/ (Markdown: https://insights.sbomify.com/CVE-2025-57440/index.md)
```

## Sources

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

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