# CVE-2026-96293: Endpoint Security Cleartext Storage of FileVault Recovery Key in Log File


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-vq33-hqqq-p4pj

## What is CVE-2026-96293?

CVE-2026-96293 is a medium-severity vulnerability in WatchGuard Agent, published on 22 Oct 2026. 

### Official description

A cleartext storage of sensitive information vulnerability in WatchGuard Endpoint Security's Full Disk Encryption feature for macOS allows a local, unprivileged user or process to obtain a managed computer's FileVault Personal Recovery Key by reading a persistently written diagnostic log file left readable by all local users.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-532 (Insertion of Sensitive Information into Log File), CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2026-96293?


## How do I fix CVE-2026-96293?

No fix has been published for CVE-2026-96293 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-96293 being exploited?

There is no known exploitation of CVE-2026-96293 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96293 and fix it if it is affected.

What it is: CVE-2026-96293 is a medium-severity vulnerability in WatchGuard Agent, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-96293 in the wild and no public exploit code.

Affected product: WatchGuard Agent. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-96293/ (Markdown: https://insights.sbomify.com/CVE-2026-96293/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-96293
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-96293
- OSV: https://osv.dev/vulnerability/CVE-2026-96293

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-96293/
Summaries are generated and may contain mistakes; the official description above is the record.