# CVE-2025-6532: NOYAFA/Xiami LF9 Pro RTSP Live Video Stream Endpoint access control

> An attacker on the local network can access the RTSP live video stream without proper authorization, exposing sensitive video data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2025
- **Updated:** 25 Jun 2025
- **Also known as:** GHSA-7vx6-qm24-765q

## What is CVE-2025-6532?

CVE-2025-6532 is a medium-severity missing authorization vulnerability in NOYAFA LF9 Pro, published on 24 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as problematic was found in NOYAFA/Xiami LF9 Pro up to 20250611. Affected by this vulnerability is an unknown functionality of the component RTSP Live Video Stream Endpoint. The manipulation leads to improper access controls. The attack can only be initiated within the local network. The exploit has been disclosed to the public and may be used. This dashcam is distributed by multiple resellers and different names.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Noyafa Lf9 Pro Firmware.

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

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

## Is CVE-2025-6532 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6532 is a medium-severity missing authorization vulnerability in NOYAFA LF9 Pro, published on 24 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6532 exists.

Affected product: NOYAFA LF9 Pro. 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-6532/ (Markdown: https://insights.sbomify.com/CVE-2025-6532/index.md)
```

## Sources

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

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