CVE-2026-18267 — Kenwood DNR1007XR Firmware Update Link Following Code Execution Vulnerability

Kenwood DNR1007XR Firmware Update Link Following Code Execution Vulnerability. This vulnerability allows physically present attackers to execute arbitrary code on affected installations of Kenwood DNR1007XR devices. Authentication is not required to exploit this vulnerability. The specific flaw exists within the firmware update process. By creating a symbolic link, an attacker can abuse the service to move a file to an arbitrary location. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-28751.

Published Aug 20, 2026Updated Aug 20, 2026Sources: cvelistV5, zdi

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

kenwood

dnr1007xr

CVSS base

6.8

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

kenwood

Products (1)

dnr1007xr

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
6.8	CVSS 3.0	MEDIUM	—	—	cvelistV5

Weakness & attack patterns

CWE-59

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

T1547.009Boot or Logon Autostart Execution: Shortcut Modification
T1574.005Hijack Execution Flow: Executable Installer File Permissions Weakness
T1574.010Hijack Execution Flow: Services File Permissions Weakness

References

2 on the record

www.zerodayinitiative.com/advisories/ZDI-26-484/
x_research-advisory
www.kenwood.com/cs/ce/mm/firmware/2020/2020f/eng.html
vendor-advisory

Elsewhere on this site

kenwoodevery CVE for this vendor
CWE-59other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.