A remote attacker does not need to log in. WatchGuard rates it 9.2 Critical under CVSS 4.0. Exposure requires a SIP proxy configured on the Firebox and a request through a policy using it.
What it allows
A crafted request through a SIP proxy policy can let an unauthenticated remote attacker run arbitrary code. The WatchGuard CNA lists a stack-based buffer overflow, unchecked buffer copying, and an out-of-bounds write among the weakness types.
The required configuration matters as much as the version. WatchGuard states that a SIP proxy must be configured on the Firebox. This record must not be read as a claim that all Fireboxes or all Fireware policies are exposed.
WatchGuard published its advisory on October 27, 2026. It says it is not aware of exploitation in the wild. That statement is attributed to the vendor; exploitation status remains unknown here. A technical severity rating does not establish that a compromise occurred.
Who is affected
For the default modern release track, WatchGuard lists Fireware versions from 2025.1 up to, but not including, 2026.4 as affected. The fixed release is 2026.4.
For the default 12.x track, the affected range starts at 12.0 and ends before 12.12.4. The fixed release is 12.12.4.
For T15 and T35 devices, the affected range starts at 12.0 and ends before 12.5.22. The fixed release is 12.5.22. This device-specific row should not be replaced with the default 12.x threshold.
All these version checks retain the SIP proxy configuration requirement. Record the Firebox model, active policy and running build before selecting the fix.
Use the WatchGuard SIP proxy patch checklist for the policy-to-verification workflow. The remote code execution glossary explains the impact, while our patch management entry covers rollout and verification.
The CVE was absent from CISA KEV catalog version 2026.10.28, fetched on October 29, 2026. That dated catalog fact does not prove that attacks cannot occur.
Timeline
- 27 Oct 2026
WatchGuard publishes the advisory and CNA record, including fixed Fireware release tracks.
- 29 Oct 2026
This profile checks the vendor scope and CISA KEV catalog version 2026.10.28; the CVE is absent from that catalog.
What to do
-
Check the SIP Proxy Policy
Review the active configuration, not just the asset inventory. Record whether a SIP proxy is configured and which policy uses it. Keep an unclear configuration open for the firewall owner to check.
-
Match the Device and Release Track
Read the installed Fireware release and Firebox model. Use the correct default or T15/T35 row. Select the matching fixed release and read its vendor release notes before the change.
-
Use the Vendor Upgrade Procedure
Confirm a usable backup and follow the procedure for the management method in use. When using WatchGuard System Manager, check its version against the target Fireware release.
-
Verify the Running Result
After the approved upgrade, record the running release again and test the expected SIP service. Attach the policy, build and service evidence to the change record.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-93857 in Brandefense Atlas
The Atlas record of CVE-2026-93857: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What Configuration Does CVE-2026-93857 Require?
WatchGuard requires a SIP proxy configured on the Firebox. The crafted request goes through a policy that uses that proxy. An affected release alone does not establish this configuration.
Are the Same Fixed Versions Used for All Devices?
No. WatchGuard lists 2026.4 and 12.12.4 for the default release tracks. T15 and T35 have a separate fixed release of 12.5.22.
Does the Critical Rating Confirm Exploitation?
No. WatchGuard says it is not aware of exploitation in the wild. The rating describes technical severity, and this profile keeps exploitation status unknown.
Sources
- CVE-2026-93857 Security AdvisoryWatchGuard PSIRT
- CVE-2026-93857 CNA RecordWatchGuard / CVE Program
- Upgrade Fireware or WatchGuard System ManagerWatchGuard
- Known Exploited Vulnerabilities CatalogCISA