SECURITYCRITICALCVE-2026-36433

CVE-2026-36433: Actions Semiconductor Media Player Utilities RCE

A physically-proximate attacker can execute arbitrary code via Production.dll and RdiskUpgrade.exe in Actions Semiconductor's Media Player Utilities v4.46.

Dylan H.

Security Team

September 10, 2026
3 min read
CVE-2026-36433: Actions Semiconductor Media Player Utilities RCE

Critical severity

Rated critical. Prioritise patching — see the remediation guidance below.

Affected Products

  • Actions Semiconductor Co. Ltd Tool- Media Player Utilities v4.46

Overview

A critical arbitrary code execution vulnerability has been disclosed in Actions Semiconductor Co. Ltd's Tool- Media Player Utilities v4.46, the production and firmware-flashing toolset used to manufacture and service MP3 players and other digital audio hardware built on the Actions Semiconductor chipset. Tracked as CVE-2026-36433, the flaw allows a physically-proximate attacker to execute arbitrary code through the Production.dll and RdiskUpgrade.exe components.

The vulnerability was published to the National Vulnerability Database on September 9, 2026, and carries a CVSS score of 9.8, reflecting the severity of the code-execution primitive once an attacker has the required proximity to a vulnerable host.


Technical Details

FieldValue
CVE IDCVE-2026-36433
SeverityCritical (CVSS 9.8)
Attack VectorPhysical / USB (proximate attacker)
AuthenticationNone Required
Affected ComponentProduction.dll, RdiskUpgrade.exe
Affected ProductTool- Media Player Utilities v4.46

How It Works

The Media Player Utilities suite is used during manufacturing and repair to flash firmware onto Actions Semiconductor-based devices — the chipset architecture that underpins a large family of budget MP3 players, digital voice recorders, and audio equipment, including hardware historically shipped under brands such as iRiver. Production.dll and RdiskUpgrade.exe handle low-level communication with connected devices over USB during the firmware upgrade and production-test workflow.

CVE-2026-36433 arises from insufficient validation of data exchanged during this USB handshake. An attacker with physical access to a host running the utility — or a maliciously crafted USB device presented to that host — can trigger arbitrary code execution in the context of the utility process. Because the flaw sits in the production tooling rather than the end-user device firmware, exploitation requires proximity to a workstation running the vulnerable software, not merely a compromised audio player in the field.


Impact Assessment

Who Is At Risk

  • Contract manufacturers and repair shops still running Media Player Utilities v4.46 to service Actions Semiconductor-based hardware
  • Refurbishment and testing facilities that plug in unknown or customer-supplied devices for diagnostics
  • Any workstation where the utility is exposed to untrusted USB peripherals

Potential Attack Chains

  1. Physical or USB Access — Attacker gains momentary physical access to a host running the utility, or supplies a maliciously crafted USB device for "repair"
  2. Malformed Handshake — Crafted data is returned during the Production.dll/RdiskUpgrade.exe communication sequence
  3. Arbitrary Code Execution — The utility process executes attacker-controlled code
  4. Persistence / Pivot — Code execution on the production workstation can be leveraged to tamper with firmware images flashed to subsequent devices, or to pivot into the broader manufacturing network

Mitigation

Immediate Actions

  • Restrict physical access to workstations running Media Player Utilities to trusted personnel only
  • Treat all inbound USB devices as untrusted during diagnostic or repair workflows — avoid plugging in customer-supplied or unknown hardware to production-tooling hosts
  • Isolate production/repair workstations from corporate and internet-facing networks
  • Given the age of the chipset family, check with Actions Semiconductor or downstream device vendors for an updated utility build; patch availability for legacy production tooling may be limited

Defence-in-Depth

  • Use USB port-control or allow-listing software to block unauthorized device classes on tooling workstations
  • Run production/repair utilities in a sandboxed or disposable VM where feasible
  • Log and monitor USB device connection events on affected hosts

References