# CVE-2026-66887: Missing Authorization in Digital Watchdog VMAX DVR and NVR Product Lineups

> Attackers can perform unauthorized state-changing actions on Digital Watchdog DVR and NVR devices due to missing authorization checks on CGIs.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA: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:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-294r-hwg8-m55w

## What is CVE-2026-66887?

CVE-2026-66887 is a critical missing authorization vulnerability in Digital Watchdog VA1G4 Recorder, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The affected products are missing authorization on state-changing CGIs and session checks are not performed.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-66887 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-66887 is a critical missing authorization vulnerability in Digital Watchdog VA1G4 Recorder, published on 15 Sep 2026. 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-2026-66887 in the wild and no public exploit code.

Affected product: Digital Watchdog VA1G4 Recorder. 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-66887/ (Markdown: https://insights.sbomify.com/CVE-2026-66887/index.md)
```

## Sources

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

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