CVE-2025-3499: Radiflow iSAP Smart Collector · ’OS Command Injection’
Affects Radiflow iSAP Smart CollectorSource CVE Database V5
Not known to be exploited · CVSS 10.0 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Radiflow iSAP Smart Collector | Affected
| Fixed in– |
AI-suggested
Immediate mitigation steps include isolating the affected iSAP Smart Collector devices from untrusted networks and restricting access to the management network ports 8084 and 8086 using network segmentation and firewall rules. Organizations should implement strict access controls, allowing only trusted administrators to reach these APIs. Monitoring network traffic for unusual commands or connections to these ports can help detect exploitation attempts. Since no patches are currently available, consider deploying virtual patching via intrusion prevention systems (IPS) that can detect and block OS command injection patterns targeting these APIs. Vendors and users should prioritize obtaining and applying vendor-supplied patches or firmware updates as soon as they are released. Additionally, conducting a thorough audit of all devices running version 1.20 and replacing or upgrading them if patching is not feasible is recommended. Implementing application-layer gateways or API gateways that validate and sanitize inputs before forwarding requests to the device can also reduce risk. Finally, reviewing and enhancing logging and alerting on these devices will improve incident response capabilities.
Description
The device has two web servers that expose unauthenticated REST APIs on the management network (TCP ports 8084 and 8086). Exploiting OS command injection through these APIs, an attacker can send arbitrary commands that are executed with administrative permissions by the underlying operating system.