WatchGuard Firebox System Integrity Check Bypass
A vulnerability in WatchGuard Fireware OS may allow an attacker to bypass the Fireware OS filesystem integrity check and maintain limited persistence via a maliciously-crafted firmware update package.
- Published
- Mar 3, 2026
- Updated
- Aug 10, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- CWE-440
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · WatchGuard
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| watchguard | fireware | cpe:2.3:o:watchguard:fireware |
| watchguard | firebox m270 | cpe:2.3:h:watchguard:firebox_m270 |
| watchguard | firebox m290 | cpe:2.3:h:watchguard:firebox_m290 |
| watchguard | firebox m370 | cpe:2.3:h:watchguard:firebox_m370 |
| watchguard | firebox m390 | cpe:2.3:h:watchguard:firebox_m390 |
| watchguard | firebox m440 | cpe:2.3:h:watchguard:firebox_m440 |
| watchguard | firebox m4600 | cpe:2.3:h:watchguard:firebox_m4600 |
| watchguard | firebox m470 | cpe:2.3:h:watchguard:firebox_m470 |
| watchguard | firebox m4800 | cpe:2.3:h:watchguard:firebox_m4800 |
| watchguard | firebox m5600 | cpe:2.3:h:watchguard:firebox_m5600 |
| watchguard | firebox m570 | cpe:2.3:h:watchguard:firebox_m570 |
| watchguard | firebox m5800 | cpe:2.3:h:watchguard:firebox_m5800 |
and 27 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- watchguard fireware12.0 and later · before 12.11.8
- watchguard fireware12.5.9 and later · before 12.5.17
- watchguard fireware2025.1 and later · before 2026.1.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WatchGuard). Independent of NVD's CPE analysis and usually ahead of it.
WatchGuard Fireware OS
- 2025.1 and later · before 2026.1.2affected
- 12.0 and later · before 12.11.8affected
- 12.0 and later · before 12.5.17affected
Same product
watchguard: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-9242WatchGuard Firebox iked Out of Bounds Write VulnerabilityKEV94Now
- CVE-2022-26318On WatchGuard Firebox and XTM appliances, an unauthenticated user can execute arbitrary code, aka FBX-22786.KEV92Now
- CVE-2025-14733WatchGuard Firebox iked Out of Bounds Write VulnerabilityKEV75This week
- CVE-2022-23176WatchGuard Firebox and XTM appliances allow a remote attacker with unprivileged credentials to access the system with a privileged managemenKEV68This week
- CVE-2013-6021Buffer overflow in WGagent in WatchGuard WSM and Fireware before 11.8 allows remote attackers to execute arbitrary code via a long sessionid41Plan
- CVE-2022-31789An integer overflow in WatchGuard Firebox and XTM appliances allows an unauthenticated remote attacker to trigger a buffer overflow and pote40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-1394089 days apartWatchGuard Firebox Boot Time System Integrity Check Bypass26Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-440 · Expected Behavior ViolationCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.