# CVE-2026-0853: A-Plus Video Technologies｜NVR - Sensitive Data Exposure

> Unauthenticated remote attackers can access the debug page to obtain sensitive device status information on A-Plus Video Technologies NVRs.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2026
- **Updated:** 12 Jan 2026
- **Also known as:** GHSA-mqqc-qq8p-5w3r

## What is CVE-2026-0853?

CVE-2026-0853 is a medium-severity vulnerability in A-Plus Video Technologies AP-BS404, published on 12 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain NVR models developed by A-Plus Video Technologies has a Sensitive Data Exposure vulnerability, allowing unauthenticated remote attackers to access the debug page and obtain device status information.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2026-0853?


## How do I fix CVE-2026-0853?

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

## Is CVE-2026-0853 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0853 and fix it if it is affected.

What it is: CVE-2026-0853 is a medium-severity vulnerability in A-Plus Video Technologies AP-BS404, published on 12 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0853 in the wild and no public exploit code.

Affected product: A-Plus Video Technologies AP-BS404. 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-2026-0853/ (Markdown: https://insights.sbomify.com/CVE-2026-0853/index.md)
```

## Sources

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

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