WatchGuard Endpoint Protection Local Privilege Escalation in Console-Service Communication Allows SYSTEM Code Execution
Affects WatchGuard Endpoint Security on Windows before 8.00.26.0011, where a local low-privileged user can run code as SYSTEM. The fix is in 8.00.26.0011.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.00.26.0011
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. WatchGuard Endpoint Protection Windows versions before 8.00.26.0011
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The WatchGuard Endpoint Protection software has a local privilege escalation flaw in how its console and protection service communicate. A local user with low-privileged credentials can inject code into the trusted console process and send privileged commands to the service, running arbitrary code with SYSTEM privileges.
Read the original description
A privilege escalation vulnerability in WatchGuard Endpoint Protection's inter-process communication between the console and the protection service allows a local, low-privileged authenticated user to execute arbitrary code with SYSTEM privileges by injecting code into the trusted console process and issuing privileged commands to the service.
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.5/10CVSS 8.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
WatchGuard Endpoint Protection Windows versions before 8.00.26.0011Upgrade to a fixed version: 8.00.26.0011.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-57907 (WatchGuard Endpoint Protection Local Privilege Escalation in Console-Service Communication Allows SYSTEM Code Execution), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-57907 (entry last updated 2026-11-10): Affected: - WatchGuard Endpoint Security: fixed in 8.00.26.0011 Fixed versions: 8.00.26.0011. Conditions (all must be true for the bug to be hit): - WatchGuard Endpoint Protection Windows versions before 8.00.26.0011 (source: https://psirt.watchguard.com/CVE-2026-57907) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: local access, low-privilege login, no user action. CISA KEV: CVE-2026-57907 is not listed as of cve.now's last read. This KEV status is for CVE-2026-57907 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://psirt.watchguard.com/CVE-2026-57907 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-57907 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-57907.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- WatchGuard Endpoint Security
fixed in 8.00.26.0011
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-57907
Is CVE-2026-57907 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A local user with low privileges who is logged in can inject code into the trusted console process and issue privileged commands to the service. This lets them run arbitrary code with SYSTEM privileges.Source: psirt.watchguard.com
Which versions are affected by CVE-2026-57907?
Endpoint Security: before 8.00.26.0011.Source: cve.now feed data
Am I affected, and how do I check?
WatchGuard Endpoint Protection on Windows, all versions before 8.00.26.0011. Compare the installed product version against 8.00.26.0011 to see whether it falls in the affected range.Source: psirt.watchguard.com
How do I fix CVE-2026-57907?
Upgrade to WatchGuard Endpoint Security 8.00.26.0011 or later, which contains the fix.Source: psirt.watchguard.com