CVE-2023-26236
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in WatchGuard EPDR 8.0.21.0002. Due to a weak implementation of message handling between WatchGuard EPDR processes, it is possible to perform a Local Privilege Escalation on Windows by sending a crafted message to a named pipe.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWatchGuard EPDR 8.0.21.0002 contains a weak implementation of inter-process message handling via named pipes, allowing a local attacker to send crafted messages that can lead to privilege escalation from a low-privileged user context to elevated system privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 8.00.22.0010< 8.00.22.0010< 8.00.22.0010< 8.00.22.0010CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed WatchGuard product versionCheck the installed version of WatchGuard EPDR, EDR, EPP, or Panda Ad360. This is typically found in the application GUI under 'About' or 'Help', or via the command line using the product's built-in version command (often 'wgem --version' or accessible via the management console).Affected if The installed version is lower than 8.00.22.0010 for any of the WatchGuard products (EPP, EDR, EPDR, or Panda Ad360).
-
Locate the inter-process named pipeIdentify the named pipe used by WatchGuard for IPC. On Windows systems, this typically involves checking for named pipe objects in the Windows Object Manager, often visible via tools like 'pipelist' from Sysinternals or by reviewing the WatchGuard service process for pipe creation. The pipe name often follows a pattern related to the product (e.g., 'WatchGuardEPDR*' or similar).Affected if A named pipe associated with WatchGuard is present and accessible for inter-process communication.
-
Verify permissions on the named pipeUse tools like 'accesschk' from Sysinternals or PowerShell 'Get-Acl' on the identified named pipe object to examine the security descriptor. Check which users and groups have write or read access to the pipe.Affected if Low-privileged (non-admin) users have write or read access to the WatchGuard named pipe, allowing them to send crafted messages.
-
Test for unauthorized process communicationMonitor or attempt to open a client connection to the WatchGuard named pipe from a low-privileged user context. Use a tool or script that attempts to connect to the pipe and send test data, observing whether the connection is accepted.Affected if A low-privileged user account can successfully connect to and send messages through the WatchGuard named pipe.
If the installed WatchGuard EPDR/EPP/EDR/Panda Ad360 version is below 8.00.22.0010 AND the inter-process named pipe is accessible to low-privileged users, the environment is vulnerable to privilege escalation via CVE-2023-26236.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.00.22.0010
Apply the vendor-supplied patch or update to a patched version of WatchGuard EPDR. As an interim measure, restrict local user access and monitor for unauthorized process communication to the vulnerable named pipe.
WatchGuard EPDR/Edr/Epp/Epdr/Panda Ad360 Firmware version 8.00.22.0010 or later
- Download WatchGuard EPDR version 8.00.22.0010 or later from the official WatchGuard support portal
- Ensure you have administrative privileges on the Windows system
- Back up current configuration and policies
- Deploy the firmware update using WatchGuard's standard update mechanism
- Verify the update was successful by checking the installed version in the EPDR console
- Restart the EPDR services if prompted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26236 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-26236 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data