CVE-2026-60095
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVinchin 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVinchin Backup & Recovery through 9.0.0.86562 has a stack buffer overflow in the ModuleHandShake function of the agentlink_server service. The vulnerability occurs because the _listen_uuid field is measured via strlen() and then copied using strcpy() into a fixed-length stack buffer without bounds checking, allowing unauthenticated attackers to overwrite the saved return address and potentially hijack control flow.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Vinchin Backup & Recovery installationCheck for the presence of Vinchin installation directories (commonly C:\Vinchin or /opt/vinchin on Linux) and locate the agentlink_server executableAffected if The product is installed and the version is 9.0.0.86562 or earlier (any version through this release)
-
Confirm installed version numberLocate the version file or executable metadata for Vinchin Backup & Recovery; compare the version to 9.0.0.86562Affected if The installed version is 9.0.0.86562 or any earlier version within the same release line
-
Verify agentlink_server service is runningQuery the running processes or service status for agentlink_server (e.g., sc query agentlink_server on Windows, ps aux | grep agentlink_server on Linux)Affected if The agentlink_server service is active and the product version is within the affected range
-
Check network exposure of the agentlink_serverIdentify which port the agentlink_server service is listening on (e.g., netstat -anp | grep agentlink_server or via the Vinchin management console)Affected if The service is exposed on a network accessible to unauthenticated attackers and the version is affected
If Vinchin Backup & Recovery version 9.0.0.86562 or earlier is installed with the agentlink_server service running and network-accessible, the environment is affected by this stack buffer overflow vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement bounds checking before string copy operations and replace strcpy() with safer alternatives like strncpy() or strlcpy() that enforce buffer length limits. Additionally, validate input length against the destination buffer size before copying.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-60095 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data