Insecure Deserialization in WatchGuard Fireware OS Access Portal
CVE-2026-4266 is an insecure deserialization vulnerability in WatchGuard Fireware OS affecting the Access Portal component. Successful exploitation allows arbitrary code execution in the context of the portald user. The flaw is not described as a standalone remote entry point; exploitation requires the attacker to have already obtained write access to the local filesystem through another vulnerability, making it a chained or post-compromise issue. Affected versions are Fireware OS 12.1 through 12.11.8 and 2025.1 through 2026.1.2. Firebox platforms that do not support the Access Portal feature, including the T15 and T35, are not affected.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
An attacker who can satisfy the prerequisite of local filesystem write access can leverage the deserialization flaw to execute arbitrary code as the portald user. This can compromise the confidentiality, integrity, and availability of the affected appliance within the privileges and reach of that service account, and may enable further post-exploitation activity depending on local privilege boundaries and service trust relationships.
If you can’t patch tonight, do this now.
No specific workaround is documented in the available information. Risk reduction depends on preventing the prerequisite condition for exploitation by eliminating other vulnerabilities that could grant local filesystem write access, restricting administrative and local write capabilities, minimizing exposure of the Access Portal feature where not required, and prioritizing upgrades on platforms that support Access Portal. Platforms without Access Portal support are not affected by this issue.
Patch, then assume compromise.
Upgrade WatchGuard Fireware OS to a fixed release. Based on the affected-version information, remediation is to move to Fireware OS 12.12 or later on the 12.x branch, or 2026.2 or later on the 2025/2026 branch, and follow the vendor security advisory for the appropriate supported release path.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.