# CVE-2025-56438: Privilege escalation in n/a

> Unauthenticated attackers with physical proximity can escalate privileges to root on Nous W3 Smart WiFi Cameras by inserting a malicious SD card.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-jrp6-pgv2-ch5v

## What is CVE-2025-56438?

CVE-2025-56438 is a medium-severity vulnerability in n/a, published on 24 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in the firmware update mechanism of Nous W3 Smart WiFi Camera v1.33.50.82 allows unauthenticated and physically proximate attackers to escalate privileges to root via supplying a crafted update.tar archive file stored on a FAT32-formatted SD card.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2025-56438 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56438 is a medium-severity vulnerability in n/a, published on 24 Oct 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-56438 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-56438/ (Markdown: https://insights.sbomify.com/CVE-2025-56438/index.md)
```

## Sources

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

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