dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2026-60094

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 · unedited
Vinchin Backup & Recovery through 9.0.0.86562 contains a heap buffer overflow vulnerability that allows unauthenticated remote attackers to cause process crash or memory corruption by sending a malformed TCP packet with an unchecked body_len field to the agentlink_server service. Attackers can craft a malicious packet that passes an attacker-controlled length directly to recv(), triggering a heap overflow of up to approximately 4 GiB and resulting in process crash or potential memory corruption.

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 confidence

Vinchin Backup & Recovery agentlink_server service contains a heap buffer overflow where an unchecked body_len field from a malformed TCP packet is passed directly to recv(), allowing attackers to trigger heap overflows of up to approximately 4 GiB, causing process crash or potential memory corruption.

MitigationImplement strict validation of the body_len field before passing it to recv(), including bounds checking against maximum allowed size and ensuring the length is within reasonable limits for the available buffer allocation.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Vinchin Backup & Recovery installation and version
    Locate the Vinchin installation directory and check the product version file, or run: vinchin --version or check the About section in the management console
    Affected if The installed version falls within the vulnerable version range (compare your version to the vendor's official vulnerability advisory)
  2. Confirm agentlink_server service is running
    Check if the agentlink_server process is active: on Windows, open Services and look for 'Vinchin AgentLink Server' or run 'sc query agentlink_server'; on Linux, run 'ps aux | grep agentlink_server' or 'systemctl status vinchin-agentlink'
    Affected if The agentlink_server service is running and exposed to network traffic
  3. Check network exposure of agentlink_server
    Identify which port agentlink_server listens on (typically TCP port 10001 or as configured), then check listening status using 'netstat -an | grep <port>' or 'ss -tlnp | grep <port>'
    Affected if The service is bound to a network interface accessible to attackers (0.0.0.0 or external IP rather than 127.0.0.1/localhost)
  4. Inspect service configuration for security settings
    Examine the agentlink_server configuration file (typically in the Vinchin config directory) for any authentication, encryption, or access control settings related to TCP packet handling
    Affected if No packet validation or body_len bounds checking is configured (the vulnerability exists regardless of config, but this confirms exposure)

You are affected if Vinchin Backup & Recovery with a vulnerable version is installed, the agentlink_server service is running, and it is network-accessible to receive malformed TCP packets with an unchecked body_len field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict validation of the body_len field before passing it to recv(), including bounds checking against maximum allowed size and ensuring the length is within reasonable limits for the available buffer allocation.

Recommended fix Moderate confidence

Vinchin Backup & Recovery version newer than 9.0.0.86562 (contact vendor for exact fixed release)

  1. 1. Identify the current installed version of Vinchin Backup & Recovery by checking the agentlink_server service or the product UI
  2. 2. Contact Vinchin support or check the official Vinchin website (www.vinchin.com) for the latest stable release that addresses this vulnerability
  3. 3. Before upgrading, ensure you have a complete backup of the Vinchin configuration and data
  4. 4. Schedule a maintenance window for the upgrade process
  5. 5. Download the latest Vinchin Backup & Recovery version from the official vendor website or official distribution channels
  6. 6. Follow Vinchin's official upgrade documentation to install the update
  7. 7. After upgrade, verify the agentlink_server service is running correctly
  8. 8. Test basic backup and recovery operations to confirm system functionality
Caveat Review Vinchin release notes for any configuration or feature changes between versions; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-60094 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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