# CVE-2026-60095: Vinchin Backup & Recovery 9.0.0.86562 Stack Buffer Overflow via ModuleHandShake

> Unauthenticated remote attackers can trigger a stack buffer overflow in Vinchin Backup & Recovery via the ModuleHandShake function, potentially achieving code execution or crashing the service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-34r7-v6pv-xq6v

## What is CVE-2026-60095?

CVE-2026-60095 is a medium-severity memory corruption vulnerability in Vinchin Backup & Recovery 9.0, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vinchin Backup & Recovery through 9.0.0.86562 contains a stack buffer overflow vulnerability in the ModuleHandShake function of the agentlink_server service that allows unauthenticated remote attackers to overwrite the saved return address by supplying an oversized _listen_uuid field that is measured via strlen() and copied without bounds checking into a fixed-length stack buffer using strcpy(). Attackers can send a crafted request with a malicious _listen_uuid value to corrupt the stack and achieve process crash or potential control flow hijack without requiring authentication.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-60095 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60095 is a medium-severity memory corruption vulnerability in Vinchin Backup & Recovery 9.0, published on 9 Jul 2026. 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-2026-60095 in the wild and no public exploit code.

Affected product: Vinchin Backup & Recovery 9.0. 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-60095/ (Markdown: https://insights.sbomify.com/CVE-2026-60095/index.md)
```

## Sources

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

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