CVE-2026-18759
Local privilege escalation in ASUSTOR Backup Plan/EZSync via recoverable IPC AES key.
Is CVE-2026-18759 being exploited?
Not confirmed. CVE-2026-18759 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-18759?
CVE-2026-18759 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-18759?
Not known from our data. No patch reference has been recorded for CVE-2026-18759, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-18759 affect?
CVE-2026-18759 affects ASUSTOR Backup Plan (ABP) <= 2.0.7.10171, ASUSTOR EZSync (AES) <= 1.1.1.3113. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-18759?
Apply vendor patch when available; restrict local accounts and tighten key file permissions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated local user can recover AES key, forge encrypted IPC to read/write arbitrary files and escalate to NT AUTHORITY\SYSTEM.
Patch when possible
- affected>= ABP 2.0 and <= 2.0.7.10171
- affected>= AES 1.0 and <= 1.1.1.3113
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.