Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local authenticated foothold
-
DeliveryOpen handle to PSKMAD driver
-
ExploitBypass access-control handshake
-
ExecutionIssue arbitrary privileged driver commands
-
ImpactDisclose kernel and process memory
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to already hold a local authenticated session (PR:L) on a host where the WatchGuard endpoint security product and its PSKMAD kernel driver are installed and loaded - i.e., a managed/protected endpoint, which is the product's default deployment mode. The specific technical precondition is the ability to open a handle to the PSKMAD driver and invoke its command interface; the vulnerability is that the driver fails to enforce its access-control handshake, so no special non-default configuration is needed once the driver is running. Limiting factors: no remote exploitation (AV:L), the attacker must first gain any valid local account, and exposure is confined to systems where the vulnerable driver version is deployed; no user interaction is required (UI:N). |
| Impact | This is a genuine high-priority local privilege/disclosure flaw, not an inflated high-CVSS paper risk, but its reach is bounded by requiring prior local authenticated access. The vendor-supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N) consistently describes a locally-exploitable, low-privilege, no-interaction attack with high impact, which aligns cleanly with the CWE-306 missing-authentication description - the signals are internally consistent rather than conflicting. The key limiting signal is AV:L combined with PR:L: an attacker must already be an authenticated local user on the endpoint, so this is a privilege-escalation/sensitive-memory-disclosure primitive rather than a remotely wormable breach. No EPSS score, no CISA KEV listing, and no public POC were provided in the input, so there is no evidence of active exploitation - real-world urgency currently rests on severity and the sensitivity of kernel/process memory disclosure rather than on observed attacker use. One honest caveat: the description explicitly names only memory disclosure (a confidentiality outcome), yet the vendor rated VI:H/VA:H (integrity and availability) on the basis of 'arbitrary privileged commands'; this impact breadth is asserted by the vendor advisory but not fully detailed in the description, and should be verified against the WatchGuard PSIRT advisory. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged authenticated account on a Windows endpoint running WatchGuard endpoint security opens a handle to the PSKMAD kernel driver and skips the driver's access-control handshake, which is not enforced. They then issue privileged driver commands to read arbitrary kernel and other-process memory, harvesting credentials, tokens, or secrets to escalate privileges. No public exploit code was identified in the provided data, so exploitation would require custom tooling against the driver's IOCTL interface. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
The Kernel Memory Access Driver (PSKMAD) shipped with WatchGuard endpoint security products fails to enforce its access-control handshake, so a local authenticated user who can open a handle to the driver can issue arbitrary privileged commands and read kernel and process memory (CWE-306). The issue is strictly local (AV:L, PR:L, UI:N) and requires the attacker to already hold a working account on a managed endpoint where the driver is loaded, making it a privilege-escalation and memory-disclosure primitive rather than a remote entry path. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV; scope is assessed as changed (S:C) because driver-level compromise extends beyond the caller's security context.
RemediationAI
No exact fixed driver version is enumerated in the supplied intelligence, so remediation should begin by pulling the corrected build from the WatchGuard PSIRT advisory at https://psirt.watchguard.com/CVE-2026-13043 and applying it through the normal endpoint-management console: fixed-version guidance and any hotfix driver packages are published there first, and patching the PSKMAD driver requires updating the endpoint agent rather than a standalone kernel binary. Until that update is deployed, the actionable compensating controls are: (1) strip unnecessary local interactive accounts from protected endpoints and enforce least privilege, since the flaw cannot be reached without a valid local session - this shrinks the attacker pool but does not help against a user who legitimately logs in; (2) monitor and alert on unexpected handles being opened to the PSKMAD driver and on unusual driver load events (Sysmon event IDs 6 and 1, or EDR driver-load telemetry), accepting that this is detection rather than prevention and generates noise on hosts with legitimate security-tool interactions; (3) if the environment permits, temporarily restrict driver handle access via Windows object ACL hardening or an application-control/blocklist rule that prevents non-approved processes from interacting with the PSKMAD device object - the trade-off is that overly broad restrictions can break the endpoint agent's own memory-scanning features and must be tested in a pilot ring first; and (4) treat any host where a low-privileged user was active as a candidate for credential rotation and memory-secret review, because the disclosed kernel/process memory may contain reusable credentials. Because the flaw is local-only with no public exploit identified at time of analysis, emergency out-of-band action is not warranted, but the patch should be prioritized on high-value or multi-user endpoints where untrusted local accounts exist.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
At the root of this finding is CWE-306, Missing Authentication for Critical Function, applied inside Windows kernel space. PSKMAD is a kernel-mode driver that endpoint-protection software installs to arbitrate privileged memory operations; legitimate callers are expected to complete an access-control handshake before the driver will honor command requests. The vulnerability is that this handshake is not actually validated, so the driver's command interface behaves as an unauthenticated critical function that any process able to obtain a driver handle can invoke. The observable effect of a successful bypass is disclosure of kernel and process memory - data that normally requires kernel privilege and that can seed further attacks such as credential or key recovery. The CPE cpe:2.3:a:watchguard:endpoint_security:*:*:*:*:*:*:*:* is a wildcarded product pattern, meaning the tracking entry has not been version-restricted, so exposure is tied to whichever driver builds carry the flawed handshake. The published CVSS 4.0 vector (9.3) and the independent 3.1 assessment agree on the mechanics - local, low complexity, no user interaction, no special configuration once the driver is running - but the independent re-score sets impact at C:H/I:L/A:L with S:C, i.e., high confidentiality loss from memory disclosure with limited integrity and availability effects, rather than the full C:H/I:H/A:H spread implied by the 4.0 score.
Know when Watchguard gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Local authenticated user (AV:L/PR:L); driver flaw reads kernel/other-process memory beyond its authorization boundary so S:C with C:H, while integrity/availability are only plausibly affected by arbitrary commands (I:L/A:L).
Primary rating from Vendor (WatchGuard).
CVSS VectorVendor: WatchGuard
Lifecycle Timeline
2DescriptionCVE.org
A missing authentication vulnerability in the Kernel Memory Access Driver (PSKMAD) used by WatchGuard endpoint security products allows a local, authenticated attacker to bypass the driver's access-control handshake and issue arbitrary privileged commands to the driver, resulting in disclosure of kernel and process memory.
Articles & Coverage 1
Executive ViewAI
A critical flaw in the Kernel Memory Access Driver (PSKMAD) shipped with WatchGuard endpoint security products allows any user who already has a working account on a managed endpoint to escalate to kernel-level privileges and read protected kernel and process memory. Because the affected component is itself a security control, a successful attack can silently undermine the very endpoint protection leadership relies on and expose credentials, keys, and other sensitive data held in memory on that device. No patch is currently available, so exposure persists across the managed endpoint estate until WatchGuard releases a fix and organizations apply compensating controls.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict interactive logon and local administrative rights on endpoints where the driver is loaded; tighten driver device-object access control lists to deny unprivileged handles; enable and monitor EDR telemetry for anomalous PSKMAD driver IOCTLs and kernel/process memory reads; consider temporarily unloading or disabling the driver where endpoint protection remains functional without it; and maintain heightened monitoring until WatchGuard publishes a fixed version.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Watchguard
View allWatchGuard Fireware OS contains an out-of-bounds write in IKEv2 VPN handling enabling unauthenticated remote code execut
Watchguard XCS 9.2 and 10.0 before build 150522 allow remote authenticated users to execute arbitrary commands via shell
Buffer overflow in WGagent in WatchGuard WSM and Fireware before 11.8 allows remote attackers to execute arbitrary code
Remote code execution in WatchGuard Fireware OS arises from an out-of-bounds write in the iked (IKE) daemon, letting an
SQL injection vulnerability in Watchguard XCS 9.2 and 10.0 before build 150522 allows remote attackers to execute arbitr
On WatchGuard Firebox and XTM appliances, an unauthenticated user can execute arbitrary code, aka FBX-22786. Rated criti
An issue was discovered on WatchGuard AP100, AP102, and AP200 devices with firmware before 1.2.9.15. Rated critical seve
Multiple cross-site request forgery (CSRF) vulnerabilities in Hexis HawkEye G 3.0.1.4912 allow remote attackers to hijac
An issue was discovered on WatchGuard AP100, AP102, and AP200 devices with firmware before 1.2.9.15, and AP300 devices w
WatchGuard RapidStream appliances allow local users to gain privileges and execute arbitrary commands via a crafted ifco
Panda Endpoint Administration Agent before 7.50.00, as used in Panda Security for Business products for Windows, uses a
Panda Security URL Filtering before 4.3.1.9 uses a weak ACL for the "Panda Security URL Filtering" directory and install
EUVD-2026-90898
GHSA-33g3-qcrh-xvc2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB