LiveActive security incident?Get immediate response
CVE Record

CVE-2026-87827: KGUARD DVR unauthenticated remote command execution vulnerability

Certain KGUARD DVR devices running vulnerable firmware expose a system command execution service on all network interfaces without requiring authentication. A remote unauthenticated attacker with network access to the affected service can execute arbitrary system commands on the device, potentially resulting in complete compromise of the DVR. The vulnerability is known to have been exploited in the wild by the Mirai_ptea (Rimasuta) and Mirai_aurora botnets for malware propagation and subsequent DDoS activity. The vulnerability was reported to affect firmware dating from 2016, while firmware released after 2017 appears to mitigate the issue by restricting the affected service to the localhost interface (127.0.0.1) instead of exposing it on all interfaces (0.0.0.0). The affected-device list reported by Netlab includes many D1004NR, D1008NR, D1016NR, D1104, D1104NR, D1108NR, D1116NR, D1132NR, D2116NR, D97xx, D98xx, and D99xx variants and several associated hardware revisions The exploit is included in some version of rapperbot and exploited in 2026. This assignment has been made to document the active exploitation and lack of documentation from the vendor.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Vulnerable KGUARD DVRs expose a command service to the network without authentication. Anyone who can reach that service may take complete control of the recorder. Reported botnets are already abusing the weakness to spread malware and support DDoS activity, making exposed legacy devices an urgent operational risk.

Executive priority

Treat reachable legacy KGUARD DVRs as an immediate containment priority. Active botnet abuse and unauthenticated command execution create credible risks of device takeover, service disruption, network intrusion, and participation in DDoS attacks. Fund rapid inventory, isolation, firmware verification, and replacement where trustworthy remediation is unavailable.

Technical view

The affected firmware binds a system command-execution service to all network interfaces rather than localhost. Exploitation requires network reachability but no credentials or user interaction. The supplied CVSS 4.0 score is 10.0. Firmware released after 2017 reportedly restricts the service to 127.0.0.1, although authoritative vendor documentation is unavailable.

Likely exposure

Highest risk applies to listed KGUARD D1004NR, D1008NR, D1016NR, D1104-series, D11xx-series, D2116NR, D97xx, D98xx, and D99xx variants using older firmware. Internet-accessible DVRs are especially exposed. Exact affected versions and hardware revisions are incompletely documented, so model name alone cannot confirm vulnerability.

Exploitation context

Netlab reported exploitation by Mirai_ptea, also called Rimasuta, and Mirai_aurora for malware propagation and DDoS activity. The supplied record additionally reports RapperBot exploitation during 2026. CISA KEV status is false in the bundle, but the cited technical source supports observed exploitation in the wild.

Researcher notes

The evidence supports the vulnerability mechanism and observed botnet exploitation, but affected-version metadata is weak: the CVE bundle lists firmware version “0” with a default unaffected status while its narrative names many legacy models. The post-2017 binding change is reported rather than vendor-confirmed. Avoid broad conclusions beyond the listed families and validate each firmware image defensively.

Mitigation direction

  • Immediately block internet access to DVR management and command services.
  • Segment affected DVRs from business systems and restrict access to trusted administration networks.
  • Identify firmware dates and obtain the newest supported firmware from authoritative vendor channels.
  • Do not assume post-2017 firmware is safe without confirming the service binds only to localhost.
  • Replace devices that cannot receive verified secure firmware or adequate network isolation.

Validation and detection

  • Inventory KGUARD DVR models, hardware revisions, firmware versions, and network locations.
  • Review firewall, NAT, and exposure-management records for externally reachable DVR services.
  • Verify locally that the command service is not listening on external network interfaces.
  • Review DVR and network telemetry for unexpected outbound connections, scanning, malware activity, or DDoS traffic.
  • After remediation, confirm access controls and external exposure from an authorized defensive assessment point.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1188: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-87827 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——CIRCL

Vulnerability scoring details

Base CVSS 4.0 score

10Critical
CVSS 4.0 vector shape for CVE-2026-87827Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
KGUARDKGUARD_firmware0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1188 · source CWE mapping

Initialization of a Resource with an Insecure Default

Initialization of a Resource with an Insecure Default represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.