# CVE-2026-59107: Shared SSH Authentication Key in vSolution Matrix File Sharing


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-x267-47cw-28j3

## What is CVE-2026-59107?

CVE-2026-59107 is a critical vulnerability in WolfVision Cynap Pro, Cynap Core Pro, published on 26 Oct 2026. 

### Official description

A security vulnerability has been identified in the vSolution Matrix file sharing feature. A shared cryptographic trust configuration could allow an attacker who obtains the matching private key to authenticate to an affected device via SSH as root. This vulnerability affects only devices configured as a vSolution Matrix main/master station with the file sharing feature enabled.

Weakness: CWE-797 (Only Filtering Special Elements at an Absolute Position)

## Which versions are affected by CVE-2026-59107?


## How do I fix CVE-2026-59107?

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

## Is CVE-2026-59107 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59107 and fix it if it is affected.

What it is: CVE-2026-59107 is a critical vulnerability in WolfVision Cynap Pro, Cynap Core Pro, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-59107 in the wild and no public exploit code.

Affected product: WolfVision Cynap Pro, Cynap Core Pro. 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-2026-59107/ (Markdown: https://insights.sbomify.com/CVE-2026-59107/index.md)
```

## Sources

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

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