CVE-2026-13053 is a high-severity out-of-bounds write vulnerability in the WatchGuard Fireware OS CLI command handler. The flaw is a memory corruption issue in the management CLI component that can be triggered by a specially crafted CLI command. According to the provided vendor-derived context, exploitation requires an authenticated user with privileged administrative access to the device. Successful exploitation can corrupt memory in the CLI handler and lead to arbitrary code execution on affected Fireware OS systems. Affected versions are Fireware OS 11.0 through 11.12.4_Update1, 12.0 through 12.12, and 2025.1 through 2026.2.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An out-of-bounds write vulnerability in the Fireware OS CLI command handler that allows a privileged authenticated user to execute arbitrary code via a crafted CLI command.
An authenticated out-of-bounds write vulnerability in the WatchGuard Fireware OS management CLI command handler that could allow a privileged user to execute arbitrary code.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.