VulnerabilityPublished 9 Jul 2025

CVE-2025-27027: Radiflow iSAP Smart Collector · Improper Isolation or Compartmentalization

Affects Radiflow iSAP Smart CollectorSource CVE Database V5

Not known to be exploited · CVSS 4.1 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

4.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Radiflowradiflow/isap-smart-collector`pkg:deb/radiflow/isap-smart-collector`Other threats	Affected =1.20	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should first ensure that the 'vpuser' account credentials are secured with strong, unique passwords and that access is limited to authorized personnel only. Implement multi-factor authentication (MFA) for SSH access if supported by the device to reduce the risk of credential compromise. Network segmentation should be enforced to isolate the iSAP Smart Collector devices from broader network access, limiting exposure. Monitoring and logging SSH access to detect unusual login patterns or privilege escalations is critical. As an interim measure, administrators may consider restricting or disabling SSH access for the 'vpuser' account or replacing rbash with a more secure shell restriction mechanism if feasible. Regular audits of user accounts and permissions on these devices should be conducted to detect and remediate potential misuse.

Description

A user with vpuser credentials that opens an SSH connection to the device, gets a restricted shell rbash that allows only a small list of allowed commands. This vulnerability enables the user to get a full-featured Linux shell, bypassing the rbash restrictions.

Impact

For European organizations using Radiflow iSAP Smart Collector 1.20, this vulnerability poses a risk primarily in environments where the 'vpuser' account credentials are accessible or weakly protected. Since the device is used for network monitoring and security management, an attacker gaining a full shell could potentially access sensitive network data, modify monitoring configurations, or use the device as a pivot point for further attacks within the network. The confidentiality of monitoring data could be compromised, and the trustworthiness of network security monitoring could be undermined. Although the vulnerability does not directly impact system availability or integrity, the ability to execute arbitrary commands increases the attack surface and could facilitate subsequent attacks. European critical infrastructure operators and industrial control system environments that rely on Radiflow products for network security monitoring are particularly at risk. The medium CVSS score reflects that exploitation requires valid credentials, so the impact is contingent on credential compromise or insider threat scenarios.

CWE-653Improper Isolation or Compartmentalization (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.
Architecture and Design
Break up privileges between different modules, objects, or entities. Minimize the interfaces between modules and require strong access control between them.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cvcn.gov.it/cvcn/cve/CVE-2025-27027 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2025, 09:10 UTC

WeaknessesCWE-653

Technical details

References

Community reviews

Related threats