dbcve.org
Epp FirmwareOperating system · Watchguard

CVE-2023-26238

MEDIUM · 5.5 CVSS v3.1 Published 2023-10-05
Fix available
A fix is available. Upgrade to 8.00.22.0010 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
An issue was discovered in WatchGuard EPDR 8.0.21.0002. It is possible to enable or disable defensive capabilities 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 · moderate confidence

The vulnerability allows manipulation of WatchGuard EPDR endpoint protection defensive capabilities by sending crafted messages to a named pipe. An attacker with local or adjacent access could potentially disable security protections, compromising the endpoint's defense mechanisms.

MitigationApply vendor-supplied patches when available. In the interim, restrict local access to systems running EPDR and monitor for unauthorized changes to defensive capability settings.

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
Epp FirmwareOperating system
Affected:< 8.00.22.0010
Edr FirmwareOperating system
Affected:< 8.00.22.0010
Epdr FirmwareOperating system
Affected:< 8.00.22.0010
Panda Ad360 FirmwareOperating system
Affected:< 8.00.22.0010

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if WatchGuard endpoint protection is installed
    Check Windows Services for WatchGuard EPP, EDR, EPDR, or Panda Adaptive Defense 360 services, or check Program Files for WatchGuard installation directories
    Affected if The service or installation directory exists on the system
  2. Determine the installed firmware version
    Use the product's administrative UI, check the service version through Windows Services properties, or examine the main executable version in the installation directory
    Affected if You are unable to retrieve a version number or the version displayed is below 8.00.22.0010
  3. Compare against the vulnerable version threshold
    Compare the discovered firmware version to 8.00.22.0010 using numeric version comparison (major.minor.build)
    Affected if The installed version is less than 8.00.22.0010 (for example, 8.00.20.0015 or any 7.x.x.x release)
  4. Verify the product type
    Confirm whether the installed product is WatchGuard EPP, EDR, EPDR, or Panda Adaptive Defense 360 using the service name or installation metadata
    Affected if The product matches any of the four affected product names listed in the CVE

A system is affected if WatchGuard EPP, EDR, EPDR, or Panda Adaptive Defense 360 is installed with a firmware version lower than 8.00.22.0010, making it vulnerable to manipulation of security protections via named pipe messages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.00.22.0010 or later
Fixed in 8.00.22.0010
Interim mitigation

Apply vendor-supplied patches when available. In the interim, restrict local access to systems running EPDR and monitor for unauthorized changes to defensive capability settings.

Recommended fix Moderate confidence

8.00.22.0010

  1. Verify current EPDR/Edr/Epdr version by checking the product console or system information
  2. Download WatchGuard EPDR version 8.00.22.0010 or later from the official WatchGuard support portal
  3. Review WatchGuard upgrade documentation for specific upgrade prerequisites
  4. Apply the firmware upgrade in accordance with WatchGuard's standard upgrade procedure
  5. After upgrade, verify that defensive capabilities are functioning correctly
  6. Confirm the installed version is 8.00.22.0010 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Epp Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26238 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-26238 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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