# CVE-2025-8762: INSTAR 2K+/4K UART improper physical access control

> Attackers with physical access can bypass UART access controls on INSTAR cameras to gain unauthorized privileges or execute code.

- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 13 Aug 2025
- **Updated:** 13 Aug 2025
- **Also known as:** GHSA-57r6-94mj-2fjf

## What is CVE-2025-8762?

CVE-2025-8762 is a high-severity vulnerability in INSTAR 2K+, published on 13 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in INSTAR 2K+ and 4K 3.11.1 Build 1124. This issue affects some unknown processing of the component UART Interface. The manipulation leads to improper physical access control. It is possible to launch the attack on the physical device. The exploit has been disclosed to the public and may be used.

Weakness: CWE-284 (Improper Access Control), CWE-1263 (Improper Physical Access Control)

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


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

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

## Is CVE-2025-8762 being exploited?

There is no known exploitation of CVE-2025-8762 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8762 is a high-severity vulnerability in INSTAR 2K+, published on 13 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8762 in the wild and no public exploit code.

Affected product: INSTAR 2K+. 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-8762/ (Markdown: https://insights.sbomify.com/CVE-2025-8762/index.md)
```

## Sources

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

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