# CVE-2025-57441: Information disclosure in n/a

> Unauthenticated Telnet access on Blackmagic ATEM Mini Pro leaks sensitive device configuration and identifiers, aiding attacker reconnaissance.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 22 Sep 2025
- **Also known as:** GHSA-j3fm-5c8x-8rw2

## What is CVE-2025-57441?

CVE-2025-57441 is a critical 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 sensitive device and stream configuration information via an unauthenticated Telnet service on port 9990. Upon connection, the attacker can access a protocol preamble that leaks the video mode, routing configuration, input/output labels, device model, and even internal identifiers such as the unique ID. This can be used for reconnaissance and planning further attacks.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Blackmagicdesign Atem Mini Pro Firmware.

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

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

## Is CVE-2025-57441 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57441 is a critical 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-57441 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-57441/ (Markdown: https://insights.sbomify.com/CVE-2025-57441/index.md)
```

## Sources

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

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