# CVE-2025-27027: Restricted shell evasion in Radiflow iSAP Smart Collector

> Authenticated users can bypass restricted shell limitations to gain full Linux shell access on Radiflow iSAP Smart Collector devices.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2025
- **Updated:** 9 Jul 2025
- **Also known as:** GHSA-wwjg-89vg-gfhh

## What is CVE-2025-27027?

CVE-2025-27027 is a medium-severity vulnerability in Radiflow iSAP Smart Collector, published on 9 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-653 (Improper Isolation or Compartmentalization)

## Which versions are affected by CVE-2025-27027?


## How do I fix CVE-2025-27027?

No fix has been published for CVE-2025-27027 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-27027 being exploited?

There is no known exploitation of CVE-2025-27027 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27027 and fix it if it is affected.

What it is: CVE-2025-27027 is a medium-severity vulnerability in Radiflow iSAP Smart Collector, published on 9 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27027 in the wild and no public exploit code.

Affected product: Radiflow iSAP Smart Collector. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-27027/ (Markdown: https://insights.sbomify.com/CVE-2025-27027/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27027
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27027
- OSV: https://osv.dev/vulnerability/CVE-2025-27027

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27027/
Summaries are generated and may contain mistakes; the official description above is the record.