CVE-2026-19318: Fireware OS Pre-Authentication Stack Buffer Overflow in iked Allows Remote Code Execution
A stack-based buffer overflow vulnerability in the WatchGuard Fireware OS iked process allows a remote unauthenticated attacker to execute arbitrary code by sending specially crafted network traffic.
Security readout for executives and security teams
Plain-English summary
A network attacker may compromise a vulnerable WatchGuard firewall without credentials or user interaction. Successful exploitation could let the attacker run code, alter information, or disrupt the device. The potential business impact is severe because firewalls protect network boundaries, but the supplied version information is ambiguous and requires confirmation against WatchGuard’s advisory.
Executive priority
Treat this as an immediate remediation priority for internet-facing or otherwise untrusted-network-reachable devices. Assign ownership now, verify the estate against WatchGuard guidance, and expedite supported updates. Exposure cannot be reliably dismissed from the supplied version data alone.
Technical view
CVE-2026-19318 is a pre-authentication stack-based buffer overflow in the Fireware OS iked process. Specially crafted network traffic can trigger arbitrary code execution. It is rated CVSS 4.0 9.3 with low attack complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Potential exposure involves WatchGuard Fireware OS devices where iked is reachable over a network. The bundle lists version pairs 2025.0/12.0 and 12.0/2026.3, but does not clearly define affected ranges or fixed builds. No CPEs are supplied, so inventory matching requires the vendor advisory.
Exploitation context
The vulnerability is remotely reachable, unauthenticated, and low complexity according to the supplied CVSS vector. However, the bundle marks KEV false and provides no cited evidence of active exploitation or a public exploit. Treat it as highly exploitable in principle, not confirmed exploited in the wild.
Researcher notes
The record maps to CWE-121, CWE-129, and CWE-191, suggesting stack corruption associated with index or arithmetic handling. The supplied sources establish remote pre-authentication code execution but do not provide root-cause detail, affected CPEs, fixed builds, exploit availability, or forensic indicators. Avoid inferring those details.
Mitigation direction
Review WatchGuard’s advisory immediately for authoritative affected versions, fixed releases, and mitigations.
Apply the vendor-recommended fixed release after confirming device model, Fireware build, and upgrade prerequisites.
Restrict untrusted access to IKE/IPsec services where operationally possible until remediation is complete.
Increase monitoring for abnormal traffic, crashes, restarts, or unexpected behavior involving iked.
Validation and detection
Inventory every WatchGuard appliance and record its exact Fireware OS version and build.
Compare each build with WatchGuard’s current advisory because the supplied version entries are ambiguous.
Confirm which interfaces expose IKE/IPsec services and whether untrusted networks can reach them.
After remediation, verify the installed build and confirm required VPN functionality remains operational.
Review relevant device and network telemetry for iked crashes or other unexplained behavior.
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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Validation of Array Index represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Integer Underflow (Wrap or Wraparound) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.