Skip to main content
Mallory
CriticalVulnerability

CVE-2026-87827: Unauthenticated Remote Command Execution in KGUARD DVR Firmware

Published Sep 9, 2026 · Updated 18 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v4
EPSS1.1%66th percentile
CISA KEVNoNot listed
In the wildReported6 exploitation records in Mallory
IdentifiersCVE-2026-87827CWE-1188 · Initialization of a Resource with…

CVE-2026-87827 affects certain KGUARD DVR devices whose firmware exposes an unauthenticated system-command-execution service on all network interfaces. A remote attacker able to reach this service can execute arbitrary system commands, potentially completely compromising the DVR. Reported affected models include variants of D1004NR, D1008NR, D1016NR, D1104, D1104NR, D1108NR, D1116NR, D1132NR, D2116NR, D97xx, D98xx, and D99xx, including associated hardware revisions. Firmware dating from 2016 is reportedly affected; releases after 2017 appear to restrict the service to localhost, although precise affected and fixed versions are not established. Mirai_ptea (Rimasuta) and Mirai_aurora have exploited the vulnerability for malware propagation and DDoS activity. Some RapperBot versions and ClingSTUN also incorporate an exploit.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise the confidentiality, integrity, and availability of the DVR through arbitrary command execution and potentially complete device takeover. Observed abuse includes malware installation, botnet propagation, and participation in DDoS attacks. Compromised devices can also support malicious proxying and access to reachable internal systems, depending on deployed malware, routing permissions, and network segmentation.

Mitigation

If you can’t patch tonight, do this now.

Immediately block network access to the affected service using firewall ACLs and network segmentation, and remove direct Internet exposure. Disable the service where feasible or ensure it binds only to localhost. Restrict DVR management access to trusted management networks or secure gateways, and limit inbound and outbound connectivity. Investigate exposed devices for existing compromise, particularly unexpected processes, persistence changes, and anomalous outbound traffic.

Remediation

Patch, then assume compromise.

Install vendor-supported firmware verified to prevent remote access to the command-execution service. Firmware released after 2017 reportedly restricts the service to localhost, but no precise confirmed fixed release is established; verify the behavior on the specific model and hardware revision rather than relying solely on the release date. Replace or permanently isolate devices for which suitable supported firmware is unavailable.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-87827 exploited in the wild?
Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-87827?
As of Nov 4, 2026, Mallory has found no public exploit for CVE-2026-87827.
Is there a patch for CVE-2026-87827?
Install vendor-supported firmware verified to prevent remote access to the command-execution service. Firmware released after 2017 reportedly restricts the service to localhost, but no precise confirmed fixed release is established; verify the behavior on the specific model and hardware revision rather than relying solely on the release date.
How severe is CVE-2026-87827?
CVE-2026-87827 has a CVSS v4 score of 10.0 (Critical) and an EPSS score of 1.1% (66th percentile) as of Nov 4, 2026.
Activity feed

Recent activity

14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+4 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware20Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.