CyberSecBulletin
CVE-2026-103593NVD status: Awaiting Analysis

Fireware OS: Stack-based Buffer Overflow

CVE-2026-103593 is a high-severity stack-based buffer overflow vulnerability in Fireware OS from WatchGuard, with a CVSS 4.0 base score of 7.1 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists versions 2026.4, 12.12.4, 12.5.22 as the first without the flaw, so updating Fireware OS to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.1% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Fireware OS to 2026.4 or 12.12.4 or 12.5.22, whichever matches your release line, or a later version.
  2. Read the advisory on psirt.watchguard.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
WatchGuardFireware OS2025.1 up to, but not including, 2026.4; 12.0 up to, but not including, 12.12.4; 12.0 up to, but not including, 12.5.222026.4, 12.12.4, 12.5.22

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Attack requirements
PresentThe target must be in a specific state or configuration for the attack to work.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Confidentiality (vulnerable system)
NoneNo loss of confidentiality on the vulnerable system.
Integrity (vulnerable system)
HighSerious loss of integrity on the vulnerable system.
Availability (vulnerable system)
HighSerious loss of availability on the vulnerable system.
Confidentiality (other systems)
NoneNo loss of confidentiality on systems beyond the vulnerable one.
Integrity (other systems)
HighSerious loss of integrity on systems beyond the vulnerable one.
Availability (other systems)
HighSerious loss of availability on systems beyond the vulnerable one.

Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA.

Official description

A stack-based buffer overflow vulnerability in the Fireware OS logging service allows a network-adjacent attacker who can impersonate or intercept traffic to the configured log server to execute arbitrary code with root privileges by presenting a specially crafted certificate.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Stack-based Buffer Overflow

The product writes past the end of a buffer that was allocated on the stack.

How developers prevent this class of flaw

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
  • Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Implement and perform bounds checking on input.

More Stack-based Buffer Overflow vulnerabilities (CWE-121)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Fireware OS

All Fireware OS vulnerabilities

Recent Stack-based Buffer Overflow vulnerabilities

Spotted an error? Tell us.