Quick answers
- Is CVE-2026-96293 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96293 being exploited in the wild.
- How severe is CVE-2026-96293?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Watchguard Endpoint Security before 1.17.24.0000 on macOS.
- Is there a fix for CVE-2026-96293?
- Yes: fixed in Endpoint Security 1.17.24.0000 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96293 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-96293?
- Check whether you run Watchguard Endpoint Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Endpoint Security 1.17.24.0000 and later
Technical details
The vulnerability is a cleartext storage of sensitive information (CWE-312) combined with incorrect permission assignment (CWE-732) in the Full Disk Encryption feature. Diagnostic log files containing the FileVault Personal Recovery Key are written with overly permissive access controls, allowing any local unprivileged user or process to read them. An attacker with local access can retrieve the recovery key from these persistent logs and use it to unlock the encrypted disk.
Affected products
- WatchGuard Endpoint Security before 1.17.24.0000 on macOS
Timeline
- 2026-10-22: disclosed