Persistent code execution via unsigned firmware flashing
Published Sep 9, 2026 · Updated Sep 10, 2026
Missing firmware verification in Actions Semiconductor Tool-Media Player Utilities 4.46 allows physically proximate attackers to execute code. Production.dll accepts the firmware path named by the blank FWFILE setting and writes the selected image to the connected device without a signature, hash, or authenticity check. Physical USB access to a supported media player is required, and flashed attacker firmware persists across factory resets and power cycles.
Summary
What happened
Missing firmware verification in Actions Semiconductor Tool-Media Player Utilities 4.46 allows physically proximate attackers to execute code. Production.dll accepts the firmware path named by the blank FWFILE setting and writes the selected image to the connected device without a signature, hash, or authenticity check. Physical USB access to a supported media player is required, and flashed attacker firmware persists across factory resets and power cycles.
The record
- CVE
- CVE-2026-36433
- Published
- Sep 9, 2026
- Updated
- Sep 10, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347, T1601.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- ByteScan unsigned firmware-injection test casesproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo