CVE-2026-60094: Vinchin Backup & Recovery Heap Buffer Overflow (Remote Denial of Service)
Vinchin Backup & Recovery versions through 9.0.0.86562 contain a vulnerability in their agentlink_server service that allows attackers to crash the backup agent or corrupt its memory without needing credentials. An attacker sends a specially crafted network packet with an incorrect length field that tricks the service into reading far more data than allocated, potentially writing up to 4 GB of attacker-controlled data into memory. This could lead to service failure or, in theory, code execution, though the current risk is primarily denial of service and data corruption.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
- Weaknesses (CWE)
- CWE-787
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-09 / 2026-07-10
NVD description (verbatim)
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.
3 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability is a classic heap buffer overflow (CWE-787) in Vinchin's agentlink_server service. The service accepts TCP connections and reads packet body data using an unchecked body_len field from the packet header. This length value is passed directly to a recv() call without validation, allowing an attacker to specify a length much larger than the allocated heap buffer. When the service attempts to fill this oversized buffer, it overwrites adjacent heap memory. The overflow magnitude can reach approximately 4 GiB if an attacker sets body_len to its maximum value, though practical exploitation depends on heap layout, memory availability, and the service's internal buffer management. The unauthenticated, network-accessible nature of the agentlink_server makes this remotely exploitable with no prior access required.
Business impact
A successful exploit disables the Vinchin backup agent on affected systems, preventing backups from completing and potentially rendering recovery unavailable during a data loss incident. Attackers can cause repeated crashes to maintain the denial of service. While immediate code execution is not guaranteed, memory corruption could enable privilege escalation or lateral movement within the backup infrastructure. Organizations relying on Vinchin for backup and disaster recovery face reduced resilience. The impact is most severe in environments where the backup agent runs on production systems or critical infrastructure.
Affected systems
Vinchin Backup & Recovery versions up to and including 9.0.0.86562 are affected. The vulnerability exists in the agentlink_server service, which listens on the network. Any deployment of these versions with the agentlink_server exposed (whether directly or via internal network) is vulnerable. The vendors_products field in the source data is empty, so consult Vinchin's official documentation or advisory for precise affected product lines, editions, and component deployments.
Exploitability
Exploitability is high. The attack requires only network access to the agentlink_server port—no authentication, no user interaction, and no special privileges. An attacker can craft a malicious packet from any network position that reaches the service. The flaw is straightforward: unchecked length validation followed by a direct recv() call. Exploit development is feasible; however, the impact (crash or memory corruption) is more predictable than achieving reliable code execution. The vulnerability is not currently listed on CISA's Known Exploited Vulnerabilities catalog, but the simplicity of the bug and its unauthenticated nature make it attractive to threat actors.
Remediation
Immediately identify all systems running Vinchin Backup & Recovery through version 9.0.0.86562. Check Vinchin's official security advisory and product portal for a patched version addressing CVE-2026-60094—verify the patch version against the vendor's guidance, as the source data does not specify a fixed version number. If a patch is available, prioritize deployment to agents protecting critical data. If no patch is yet available, isolate agentlink_server from untrusted networks, restrict TCP access to the service port via firewall rules, and monitor for unusual connection patterns or agent crashes. Consider disabling the service temporarily if an alternative backup method exists and the risk is deemed unacceptable.
Patch guidance
Contact Vinchin directly or consult their security advisory page for the availability and version number of the patch for CVE-2026-60094. Once a patched version is confirmed, test it in a non-production environment to validate backup and recovery functionality before rolling out to production agents. Given the network-exposed nature of the service, prioritize patching agents that are internet-facing or accessible from untrusted segments. Implement a phased rollout to minimize service interruption if the patch introduces any compatibility issues.
Detection guidance
Monitor agentlink_server processes for unexpected crashes or restart loops, which may indicate exploitation attempts. Enable network intrusion detection on inbound traffic to the agentlink_server port; look for malformed TCP packets with unusually large body_len fields or packets that deviate from the expected protocol structure. Inspect the backup agent's logs for errors related to memory allocation or buffer handling. If available, deploy endpoint detection and response (EDR) tools to capture heap corruption events or unusual memory access patterns on systems running the agent. Baseline normal traffic to the service and alert on anomalies.
Why prioritize this
Although listed as MEDIUM severity (CVSS 6.5), this vulnerability warrants high prioritization due to the combination of unauthenticated network access, lack of complexity, and the critical nature of backup infrastructure. A successful attack disables a core resilience function. In environments where backup agents are exposed to less-trusted networks or the internet, prioritization should be elevated. The absence of a known public exploit does not diminish risk; the vulnerability is straightforward enough that adversaries will develop tooling quickly if they identify vulnerable deployments.
Risk score, explained
The CVSS 3.1 score of 6.5 reflects a MEDIUM base risk: network-accessible (AV:N), no authentication required (PR:N), no user interaction (UI:N), affecting only the target service (S:U), with limited integrity impact (I:L) and availability impact (A:L). The score does not account for the criticality of backup infrastructure or the potential for heap corruption to cascade into further compromise. Organizations should consider a higher contextual risk level if this service is exposed to adversary-controlled networks or if the affected backup system protects high-value data.
Frequently asked questions
Could an attacker achieve remote code execution through this vulnerability?
Direct, reliable code execution is not guaranteed by the vulnerability alone. However, heap buffer overflows can corrupt adjacent heap structures, potentially enabling exploitation techniques such as heap spraying or return-oriented programming (ROP) if the attacker can leak memory layout information. The primary observed impact is denial of service via process crash or memory corruption that halts backup operations. Whether code execution is feasible depends on the specific heap allocator, system protections (ASLR, DEP), and the agentlink_server's binary hardening.
What is agentlink_server, and why is it exposed on the network?
agentlink_server is a network service in Vinchin Backup & Recovery that communicates with backup agents and coordinates backup jobs. It is designed to listen on the network to coordinate agents across infrastructure. In properly configured environments, it should be isolated to trusted administrative networks via firewall rules. However, misconfiguration or deployment in cloud/hybrid environments may inadvertently expose it to broader networks, creating vulnerability.
If we apply a patch, do we need to restart backup jobs or reconfigure anything?
Patch deployment procedures depend on Vinchin's release notes. Typically, patching a service-side component like agentlink_server requires a restart of the service; backup jobs may be paused during the update. Consult the vendor's advisory for specific downtime and reconfiguration requirements. Test the patch in a lab environment first to validate that existing backup schedules and recovery workflows remain functional.
Is this vulnerability currently being exploited in the wild?
As of the published date (2026-07-09), the vulnerability is not listed on CISA's Known Exploited Vulnerabilities catalog. However, the ease of exploitation and the critical nature of backup infrastructure make it an attractive target. Organizations should assume active development of exploit code and monitor for signs of abuse even before public exploit code appears.
This analysis is based on the published CVE description and does not constitute legal or compliance advice. Organizations should verify all patch versions, affected product editions, and remediation steps against Vinchin's official security advisory and product documentation. CVSS scores represent base risk; contextual risk assessment appropriate to your environment and data criticality should inform prioritization decisions. No exploit code or weaponized proof-of-concept is provided or implied herein. Consult your security team and vendor support for environment-specific guidance. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2025-10238MEDIUMThinkPad BIOS Out-of-Bounds Write, SMM Code Execution Risk
- CVE-2025-59614MEDIUMQualcomm Memory Corruption in RNG Command Handling
- CVE-2026-10114MEDIUMOpen5GS Out-of-Bounds Write in NF Profile Parser
- CVE-2026-10644MEDIUMZephyr SERCOM-G1 UART Out-of-Bounds Write on PIC32CM-JH
- CVE-2026-10999MEDIUMGoogle Chrome ANGLE Integer Overflow Information Disclosure
- CVE-2026-11090MEDIUMChrome ANGLE Memory Leak Enables Cross-Origin Data Theft
- CVE-2026-12298MEDIUMMemory Safety Vulnerability in Firefox and Thunderbird
- CVE-2026-12528MEDIUM389 Directory Server Heap Buffer Overflow in ACI Parsing