CVE-2026-13086: Fireware OS Stack-Based Buffer Overflow in Mobile Security epm Endpoint
A stack-based buffer overflow in the epm (Endpoint Protection Manager) service used by the deprecated Mobile Security feature in WatchGuard Fireware OS allows an unauthenticated remote attacker to execute arbitrary code.
Security readout for executives and security teams
Plain-English summary
A flaw in WatchGuard Fireware OS’s deprecated Mobile Security service could let an unauthenticated remote attacker take control of an exposed device. Successful exploitation could compromise confidentiality, integrity, and availability. The supplied version data is internally ambiguous, so organizations should confirm applicability directly against WatchGuard’s advisory.
Executive priority
Treat as an urgent validation and remediation item for internet-facing or untrusted-network-accessible WatchGuard appliances. Require owners to establish service exposure and vendor-confirmed applicability promptly. Systems without enabled Mobile Security or reachable epm may have substantially lower exposure, but the ambiguous version data makes configuration-based verification essential.
Technical view
CVE-2026-13086 is a network-reachable stack-based buffer overflow in the epm Endpoint Protection Manager service. It requires no privileges or user interaction and may permit arbitrary code execution. CVSS 4.0 scores it 9.3. The record also lists CWE-121, CWE-787, and CWE-798, but provides no further technical detail.
Likely exposure
Exposure is most likely where the deprecated Mobile Security feature is enabled and its epm service is network-reachable. The supplied affected-version entries mention Fireware OS 12.0, 2025.0, and 2026.3 but also mark default status as unaffected, preventing a reliable version-only determination.
Exploitation context
The source bundle does not report known active exploitation, and the CVE is not identified as being in CISA KEV. Nevertheless, unauthenticated network access, low attack complexity, and potential arbitrary code execution make exposed instances high risk. No exploit prerequisites beyond service reachability are documented here.
Researcher notes
The supplied record supports remote, unauthenticated arbitrary code execution through a stack overflow, but does not provide packet structure, affected code paths, fixed versions, or exploitation evidence. Version statements are inconsistent with the listed default-unaffected status. Avoid inferring vulnerability from version alone; validate feature enablement, reachability, and WatchGuard’s current applicability table.
Mitigation direction
Review WatchGuard’s advisory for confirmed affected versions, fixed releases, and vendor-approved mitigations.
Disable the deprecated Mobile Security feature where it is not operationally required.
Restrict network access to the epm service while applicability and remediation are confirmed.
Prioritize vendor-supported remediation for any confirmed vulnerable, reachable appliance.
Validation and detection
Inventory Fireware OS appliances and record exact versions, configurations, and Mobile Security usage.
Determine whether the epm service is enabled and reachable from untrusted networks.
Compare each appliance against the current WatchGuard advisory’s affected-version criteria.
After remediation, confirm the deprecated feature or vulnerable service is disabled, restricted, or vendor-fixed.
Review monitoring data for unexpected connections or instability involving the epm service.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
4Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.