CVE-2026-22313: OS Command Injection in Radiflow iSAP Smart Collector
Critical CVSS (9.1) reachable over network.
| Field | Value |
|---|---|
| CVE ID | CVE-2026-22313 |
| CVSS score | 9.1 Critical |
| Attack vector | Network |
| Auth required | Yes, authenticated attacker with high privileges |
| Patch status | Unknown from public sources; no fixed version identified in retrieved advisories |
TL;DR - Authenticated OS command injection affects Radiflow iSAP Smart Collector version 3.07-1. - Exposure is tied to the management network REST API on TCP port 8086. - No public fix, PoC, or confirmed in-the-wild exploitation is identified; segment and restrict access now.
Vulnerability at a glance
CVE-2026-22313 is a critical OS command injection vulnerability in Radiflow iSAP Smart Collector. Publicly available advisory material describes the flaw as affecting the device web server’s REST API, exposed on the management network and specifically associated with TCP port 8086. According to the NVD description and the referenced CVCN advisory, an authenticated attacker can inject arbitrary operating system commands that execute with administrative permissions on the underlying OS.
This is not a low-privilege internet worm scenario. The CVSS vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H, which means the attacker needs valid access and the vulnerable service must be reachable over the network. Even so, the impact is severe: once the attacker reaches the vulnerable execution path, they can potentially run arbitrary commands as an administrative context, creating immediate risk to confidentiality, integrity, and availability.
Two points matter for defenders. First, this is an OT/ICS-adjacent management-plane issue, so many organizations may assume network isolation is enough. That assumption is risky if jump hosts, shared admin VLANs, VPN exposure, or flat internal routing make the management service reachable. Second, the public sources do not currently provide a patch version, so defenders need to plan around containment and monitoring rather than waiting for perfect remediation guidance.
What the vulnerability is and why it matters
The flaw is classified as CWE-78: Improper Neutralization of Special Elements used in an OS Command, commonly called OS command injection. In practical terms, the application appears to pass attacker-controlled input from a REST API request into an OS command execution path without adequate sanitization or hardening. If that description is accurate, a malicious authenticated user can supply crafted input that appends or replaces intended shell arguments.
Command injection in an appliance or collector product is especially serious because these systems often sit in trusted monitoring or collection roles. A Smart Collector may have visibility into industrial, operational, or management environments. Compromising it can therefore create both direct system risk and indirect network pivoting opportunities. Even when exploitation requires valid credentials, the blast radius can be large because management systems frequently have elevated trust relationships, stored credentials, network reachability, or access to sensitive telemetry.
The severity score of 9.1 Critical can look surprising at first because Privileges Required is High. The explanation is the outcome: the flaw yields administrative-permission command execution, and the CVSS vector includes Scope: Changed plus high impact across all CIA categories. For defenders, that means this is less about broad opportunistic exploitation and more about post-authentication takeover by an insider, a compromised admin account, or an attacker who already obtained management credentials through phishing, password reuse, VPN compromise, or lateral movement.
Technical Notes
The public advisory does not identify the exact vulnerable endpoint, parameter name, or payload format. Defenders should not invent signatures tied to a specific URI without vendor confirmation. In the absence of endpoint-level detail, focus on the known exposure points:
Known exposed surface from public sources:
- Product: Radiflow iSAP Smart Collector
- Confirmed affected version: 3.07-1
- Service type: Web server exposing REST API
- Network location: Management network
- Port: TCP 8086
- Vulnerability class: OS command injection
- Impact: Arbitrary command execution with administrative permissions
Basic validation from a network inventory perspective should start with identifying systems listening on TCP 8086:
# Find potential exposed collectors from a management segment
nmap -sV -p 8086 10.0.0.0/16
# Check whether a local host is listening on 8086
ss -ltnp | grep ':8086'
Affected products and version scope
The publicly retrieved source material confirms Radiflow iSAP Smart Collector version 3.07-1 as affected. That is the only specific version explicitly named in the available advisory content. At the time of writing, there is no broader confirmed affected version range and no public source in the provided material that says “before X” or “3.07-1 and earlier.”
That distinction matters operationally. Security teams often default to assuming adjacent builds are vulnerable, and that may be prudent for temporary risk handling, but it should be clearly labeled as an assumption rather than a confirmed fact. If you run version 3.07-1, you should treat it as affected. If you run another version, the safest language is: public sources do not currently confirm whether that version is affected or fixed.
Likewise, the fixed version number is unknown from the available primary sources. No vendor patch bulletin, hotfix reference, or release note was identified in the material provided. In environments that require formal remediation evidence, document the gap explicitly: “No fixed version was identified in retrieved public sources as of 2026-06-16.” Then escalate through vendor support or account channels for an authoritative answer.
| Product | Confirmed affected versions | Fixed version |
|---|---|---|
| Radiflow iSAP Smart Collector | 3.07-1 | Unknown from available public sources |
Technical Notes
If you need to confirm deployed versions at scale, start with asset inventory, appliance management consoles, CMDB records, or backup/export metadata. Because the public sources do not document a supported CLI version query for this product, do not rely on guessed commands in production. Use existing inventory and vendor-approved admin workflows first.
A practical interim workflow is to tag all Smart Collector assets and classify them as follows:
Status categories:
- Confirmed vulnerable: version 3.07-1
- Version unknown: treat as potentially exposed until validated
- Other version: not publicly confirmed vulnerable or fixed; verify with vendor
Exploitation status and risk assessment
Based on the supplied source material, exploitation in the wild is not confirmed. The CVE is not listed in CISA KEV at this time, which means there is no CISA-backed indication of known exploitation requiring emergency action under that catalog. That said, absence from KEV is not evidence of safety. OT and management-plane vulnerabilities are often underreported publicly, especially if exploitation occurs in tightly controlled or private environments.
A public proof of concept is also not identified in the retrieved material. No exploit repository, technical write-up, or public demonstration was cited in the provided sources. As of this writing, the correct statement is: no public PoC identified and no confirmed in-the-wild exploitation identified.
Defenders should still assume the vulnerability is exploitable by a determined attacker because the advisory provides enough detail to establish the primitive: authenticated command injection on a known management service and port. Once a flaw of that class is public, internal red teams, threat actors with appliance access, or researchers may be able to reproduce it even without a published exploit. In other words, lack of PoC lowers noise, not risk.
What defenders should do next
First, identify every Radiflow iSAP Smart Collector in your environment and confirm whether any run version 3.07-1. If version data is incomplete, treat those assets as potentially affected until verified. Asset certainty matters here because public version scope is narrow and specific, but patch scope is still unknown.
Second, treat the management API on port 8086 as sensitive attack surface. Restrict it aggressively, inventory who can reach it, and review recent authenticated access for anomalies. If your environment assumes appliance trust by default, this CVE is a good reason to revisit that assumption.
Third, open a vendor case if you need authoritative remediation details. The public source material confirms the vulnerability and affected version, but it does not confirm a fix version or official workaround. Until that changes, your most reliable defenses are segmentation, access reduction, credential review, and focused monitoring.
Detection and hunting guidance
Detection is complicated by one major limitation: the public advisory does not disclose the vulnerable endpoint or exact request pattern. That means defenders need to monitor behavioral indicators rather than one perfect signature. Start with the known control points: authentication events to the management interface, REST API requests to the service on TCP 8086, and any subsequent process execution or shell invocation on the appliance.
The most useful detection questions are straightforward. Who accessed the management API? From which source IPs and jump hosts? Did those requests occur outside normal change windows? Did the appliance spawn unusual child processes, shell interpreters, or system utilities? If the collector normally serves as a stable appliance, command execution chains such as shell, curl, wget, nc, bash, sh, python, or file archiving tools are high-value anomalies.
If you have network telemetry, look for administrative sessions from uncommon management stations and API request bursts to port 8086. If you have appliance logs, correlate successful authentication with immediate error responses, malformed parameters, or abrupt service restarts. If you have EDR or process telemetry on the underlying OS, prioritize any evidence that the web service launches OS commands.
Technical Notes
Because exact endpoint details are unknown, use broad but concrete detections around the known service:
Network/service pattern to watch:
- Destination port: 8086/TCP
- Role: Radiflow iSAP Smart Collector management network REST API
- Suspicious sequence: successful authentication followed by atypical API request bursts and shell/process activity
Example Splunk hunt for connections to the service from unexpected sources:
index=firewall OR index=netflow
dest_port=8086
| stats count min(_time) as firstSeen max(_time) as lastSeen values(src_ip) as src values(dest_ip) as dest by src_ip,dest_ip
| lookup approved_management_hosts ip as src_ip OUTPUT ip as approved_ip
| where isnull(approved_ip)
| sort - count
Example process-based hunt if the appliance logs process execution to syslog or an EDR platform:
index=edr OR index=syslog
(host="*smart-collector*" OR asset_type="Radiflow iSAP Smart Collector")
(process_name IN ("sh","bash","ash","curl","wget","nc","netcat","python","perl"))
| table _time host parent_process_name process_name process_command_line user
| sort - _time
Generic log patterns worth flagging:
Indicators to review:
- Authenticated requests to TCP/8086 from non-standard admin hosts
- HTTP 200/500 sequences on the API followed by process execution
- Parent-child relationships such as:
webserver/process -> sh
webserver/process -> bash
webserver/process -> curl
- Administrative command execution shortly after API access
Example Suricata-style watchlist concept for management access review, not exploit confirmation:
alert tcp $HOME_NET any -> $OT_MGMT_NET 8086 (msg:"Review Radiflow Smart Collector management API access"; flow:to_server,established; sid:2231301; rev:1;)
Mitigation and patching
The hardest part of this CVE is that no fixed version is identified in the available public sources. Therefore, you should not claim the issue is resolved simply by “being up to date” unless you have direct vendor confirmation. If you operate Radiflow iSAP Smart Collector version 3.07-1, the most defensible immediate action is to reduce exposure to the management API on TCP 8086 and tightly control who can authenticate to it.
In practice, that means restricting management network reachability to a very small set of hardened jump hosts, rotating credentials for all users with access to the platform, enforcing MFA where your surrounding access architecture supports it, and reviewing whether the API must remain reachable at all times. If TCP 8086 is only needed during defined administration windows, consider temporary ACLs or firewall rules that expose it only when necessary. Also review any shared service accounts, stored tokens, or VPN access paths that could satisfy the “authenticated attacker” requirement.
Because patch status is unknown, compensating controls should be treated as primary defenses, not placeholders. For OT teams, involve both security and operations before making network changes, but do not let uncertainty about a patch delay simple exposure reduction. An authenticated command injection on a management appliance is exactly the kind of flaw where segmentation, credential hygiene, and access minimization materially lower risk.
Technical Notes
There is no vendor-provided upgrade command in the public material, so none can be stated as fact. If your organization uses package automation, do not guess an appliance update command. Instead, use explicit network and access workarounds that can be executed immediately.
Example firewall restriction on a Linux-based segmentation point to allow only an approved jump host:
# Replace values with your actual management jump host and collector IP
iptables -A INPUT -p tcp -s 192.0.2.10 -d 192.0.2.50 --dport 8086 -j ACCEPT
iptables -A INPUT -p tcp -d 192.0.2.50 --dport 8086 -j DROP
Example network policy approach with firewalld:
firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="192.0.2.10" port protocol="tcp" port="8086" accept'
firewall-cmd --permanent --add-rich-rule='rule family="ipv4" port protocol="tcp" port="8086" drop'
firewall-cmd --reload
Example review command to identify current exposure on an internal scanner or admin host:
nmap -Pn -p 8086 192.0.2.50
If you need a formal workaround statement for change control, use wording like this:
Workaround until vendor fix is confirmed:
1. Limit TCP/8086 access to dedicated management jump hosts only.
2. Remove direct user workstation access to the management network.
3. Rotate administrative credentials and API tokens tied to the platform.
4. Increase logging and monitoring for authenticated API activity.
5. Contact Radiflow support for authoritative fixed-version guidance.
References
- CVCN advisory: https://www.cvcn.gov.it/cvcn/cve/CVE-2026-22313
- CVE.org record: https://www.cve.org/CVERecord?id=CVE-2026-22313
- NVD: https://nvd.nist.gov/
For further reading on securing your AWS account, you can visit our guide on how to secure your AWS account. Additionally, understanding the implications of OS command injection can be crucial, so check out our FAQ on what is SQL injection.
This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.