# CVE-2025-35021: Abilis CPX Fallback Shell Connection Relay

> Attackers can bypass SSH authentication on unconfigured Abilis CPX devices to access a restricted shell and relay connections.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2025
- **Updated:** 5 Nov 2025
- **Also known as:** GHSA-6f2r-5p58-wvrf

## What is CVE-2025-35021?

CVE-2025-35021 is a medium-severity authentication bypass vulnerability in Abilis CPX, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

By failing to authenticate three times to an unconfigured Abilis CPX device via SSH, an attacker can login to a restricted shell on the fourth attempt, and from there, relay connections.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: Antek Abilis Cpx Firmware.

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

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

## Is CVE-2025-35021 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-35021 is a medium-severity authentication bypass vulnerability in Abilis CPX, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-35021 in the wild and no public exploit code.

Affected product: Abilis CPX. 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-35021/ (Markdown: https://insights.sbomify.com/CVE-2025-35021/index.md)
```

## Sources

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

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