CVE-2025-28236
Published: 18 April 2025
Summary
CVE-2025-28236 is a critical-severity Download of Code Without Integrity Check (CWE-494) vulnerability. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 26.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
Nautel VX Series transmitters running firmware version 6.4.0 and earlier contain a remote code execution vulnerability in the firmware update mechanism. The flaw, tracked as CVE-2025-28236 and assigned CWE-494, resides in the handling of update packages submitted to the /#/software/upgrades endpoint and carries a CVSS 3.1 base score of 9.8.
An unauthenticated attacker with network access can upload a maliciously crafted update package to achieve arbitrary code execution on the affected transmitter. Successful exploitation grants full control over the device, including the ability to modify broadcast behavior or persist access.
Public references consist of a GitHub repository containing technical details of the issue, but no vendor advisory or patch information is provided in the available sources. The EPSS score rose from a low baseline to a recorded peak of 0.0144, indicating increased exploitation interest following disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-11891
Vulnerability details
Nautel VX Series transmitters VX SW v6.4.0 and below was discovered to contain a remote code execution (RCE) vulnerability in the firmware update process. This vulnerability allows attackers to execute arbitrary code via supplying a crafted update package to the…
more
/#/software/upgrades endpoint.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Policies can require integrity verification of software prior to installation, reducing risks from unverified downloads.
Blocks installation of components lacking a valid signature, mitigating download or installation of code without integrity checks.
Acquisition and maintenance portions of the strategy drive requirements for integrity verification of downloaded or supplied code.
Mandating integrity control and approved-only changes during development prevents incorporation of code or components lacking integrity validation.
Supply chain protection requires integrity verification of acquired components, directly reducing insertion or tampering of malicious code during delivery.
Reduces exposure to code obtained without integrity verification by requiring assurance processes that confirm authenticity and absence of tampering.
Tamper resistance and detection commonly include integrity verification of code and firmware obtained from external sources.
Component authenticity requires verifying origin/integrity of acquired firmware or software, directly preventing inclusion of code without integrity checks.