CVE-2022-26318

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 3 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 78%CVSS: 9.8Exploit: cisa kev · ssvc active · Metasploit · epss top5pct · epss high · public exploitExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

On WatchGuard Firebox and XTM appliances, an unauthenticated user can execute arbitrary code, aka FBX-22786. This vulnerability impacts Fireware OS before 12.7.2_U2, 12.x before 12.1.3_U8, and 12.2.x through 12.5.x before 12.5.9_U2.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation100% × 40%
Automatability100% × 15%
CISA SSVC: Attend at low mission impact; Act at medium or high.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.
EPSS PROB
78%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCAttend at low mission impact; Act at medium or high.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 4, 2022

Last Modified

November 13, 2025

Advisory Details (2)

Auto-updated Oct 1, 2026
⚠️ Active exploitation confirmed. No fix on record yet. Sources: cisa.
cisa🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-26318

Data Freshness Timeline

(refreshed 52× in last 7d / 235× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 971 total refreshes for this CVE.

  1. 2026-10-06 04:49 UTCGHSA enrichment
  2. 2026-10-06 01:00 UTCGHSA enrichment
  3. 2026-10-05 21:11 UTCGHSA enrichment
  4. 2026-10-05 17:21 UTCGHSA enrichment
  5. 2026-10-05 13:32 UTCGHSA enrichment
  6. 2026-10-05 09:42 UTCGHSA enrichment
  7. 2026-10-05 05:53 UTCGHSA enrichment
  8. 2026-10-05 02:04 UTCGHSA enrichment
  9. 2026-10-04 22:14 UTCGHSA enrichment
  10. 2026-10-04 18:25 UTCGHSA enrichment
  11. 2026-10-04 14:33 UTCGHSA enrichment
  12. 2026-10-04 10:43 UTCGHSA enrichment
  13. 2026-10-04 06:54 UTCGHSA enrichment
  14. 2026-10-04 03:05 UTCGHSA enrichment
  15. 2026-10-03 23:16 UTCGHSA enrichment
  16. 2026-10-03 19:26 UTCGHSA enrichment
  17. 2026-10-03 15:37 UTCEG score recompute
  18. 2026-10-03 15:37 UTCGHSA enrichment
  19. 2026-10-03 14:23 UTCEPSS rescore
  20. 2026-10-03 14:22 UTCEPSS rescore
  21. 2026-10-03 11:45 UTCGHSA enrichment
  22. 2026-10-03 07:55 UTCGHSA enrichment
  23. 2026-10-03 04:04 UTCGHSA enrichment
  24. 2026-10-03 00:15 UTCGHSA enrichment
  25. 2026-10-02 20:25 UTCGHSA enrichment
Show 75 more
  1. 2026-10-02 16:33 UTCEG score recompute
  2. 2026-10-02 16:33 UTCGHSA enrichment
  3. 2026-10-02 12:43 UTCGHSA enrichment
  4. 2026-10-02 08:54 UTCGHSA enrichment
  5. 2026-10-02 05:05 UTCGHSA enrichment
  6. 2026-10-02 01:17 UTCGHSA enrichment
  7. 2026-10-01 21:28 UTCGHSA enrichment
  8. 2026-10-01 17:39 UTCGHSA enrichment
  9. 2026-10-01 13:49 UTCGHSA enrichment
  10. 2026-10-01 10:00 UTCGHSA enrichment
  11. 2026-10-01 06:12 UTCGHSA enrichment
  12. 2026-10-01 02:23 UTCGHSA enrichment
  13. 2026-09-30 22:35 UTCGHSA enrichment
  14. 2026-09-30 18:46 UTCEG score recompute
  15. 2026-09-30 18:46 UTCGHSA enrichment
  16. 2026-09-30 15:00 UTCEPSS rescore
  17. 2026-09-30 14:58 UTCGHSA enrichment
  18. 2026-09-30 11:09 UTCGHSA enrichment
  19. 2026-09-30 07:20 UTCGHSA enrichment
  20. 2026-09-30 03:31 UTCGHSA enrichment
  21. 2026-09-29 23:43 UTCGHSA enrichment
  22. 2026-09-29 19:54 UTCGHSA enrichment
  23. 2026-09-29 16:05 UTCEG score recompute
  24. 2026-09-29 16:04 UTCGHSA enrichment
  25. 2026-09-29 15:15 UTCEPSS rescore
  26. 2026-09-29 12:15 UTCGHSA enrichment
  27. 2026-09-29 08:26 UTCGHSA enrichment
  28. 2026-09-29 04:38 UTCGHSA enrichment
  29. 2026-09-29 00:49 UTCEG score recompute
  30. 2026-09-29 00:48 UTCGHSA enrichment
  31. 2026-09-28 20:58 UTCGHSA enrichment
  32. 2026-09-28 17:09 UTCEG score recompute
  33. 2026-09-28 17:09 UTCGHSA enrichment
  34. 2026-09-28 13:48 UTCEPSS rescore
  35. 2026-09-28 13:20 UTCGHSA enrichment
  36. 2026-09-28 09:31 UTCGHSA enrichment
  37. 2026-09-28 05:43 UTCGHSA enrichment
  38. 2026-09-28 01:54 UTCGHSA enrichment
  39. 2026-09-27 22:05 UTCGHSA enrichment
  40. 2026-09-27 21:51 UTCCISA KEV update
  41. 2026-09-27 18:16 UTCGHSA enrichment
  42. 2026-09-27 14:27 UTCGHSA enrichment
  43. 2026-09-27 10:38 UTCGHSA enrichment
  44. 2026-09-27 06:46 UTCGHSA enrichment
  45. 2026-09-27 02:56 UTCGHSA enrichment
  46. 2026-09-26 23:07 UTCGHSA enrichment
  47. 2026-09-26 19:16 UTCEG score recompute
  48. 2026-09-26 19:16 UTCGHSA enrichment
  49. 2026-09-26 15:27 UTCGHSA enrichment
  50. 2026-09-26 11:38 UTCGHSA enrichment
  51. 2026-09-26 07:49 UTCGHSA enrichment
  52. 2026-09-26 04:00 UTCEG score recompute
  53. 2026-09-26 04:00 UTCGHSA enrichment
  54. 2026-09-26 00:22 UTCEPSS rescore
  55. 2026-09-26 00:09 UTCGHSA enrichment
  56. 2026-09-25 20:19 UTCGHSA enrichment
  57. 2026-09-25 19:35 UTCCISA KEV update
  58. 2026-09-25 16:30 UTCGHSA enrichment
  59. 2026-09-25 14:55 UTCCISA KEV update
  60. 2026-09-25 12:41 UTCGHSA enrichment
  61. 2026-09-25 08:52 UTCGHSA enrichment
  62. 2026-09-25 05:03 UTCGHSA enrichment
  63. 2026-09-25 01:15 UTCGHSA enrichment
  64. 2026-09-24 21:26 UTCGHSA enrichment
  65. 2026-09-24 19:31 UTCCISA KEV update
  66. 2026-09-24 17:37 UTCEG score recompute
  67. 2026-09-24 17:37 UTCGHSA enrichment
  68. 2026-09-24 14:00 UTCEPSS rescore
  69. 2026-09-24 13:48 UTCGHSA enrichment
  70. 2026-09-24 09:59 UTCGHSA enrichment
  71. 2026-09-24 06:10 UTCGHSA enrichment
  72. 2026-09-24 02:21 UTCGHSA enrichment
  73. 2026-09-23 22:33 UTCGHSA enrichment
  74. 2026-09-23 18:45 UTCGHSA enrichment
  75. 2026-09-23 14:55 UTCEG score recompute

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/linux/http/watchguard_firebox_unauth_rce_cve_2022_26318✓ verified
    First seen Aug 29, 2022

    WatchGuard XTM Firebox Unauthenticated Remote Command Execution

    Open source ↗
  • GitHub PoCBabyTeam1024/CVE-2022-26318
    First seen May 21, 2022
    Open source ↗
  • GitHub PoCh3llk4t3/Watchguard-RCE-POC-CVE-2022-26318
    First seen Apr 18, 2022

    Watchguard RCE POC CVE-2022-26318

    Open source ↗
  • GitHub PoCmisterxid/watchguard_cve-2022-26318
    First seen Mar 28, 2022
    Open source ↗

Frequently asked(6)

What is CVE-2022-26318?
CVE-2022-26318 is a critical vulnerability published on March 4, 2022. On WatchGuard Firebox and XTM appliances, an unauthenticated user can execute arbitrary code, aka FBX-22786. This vulnerability impacts Fireware OS before 12.7.2U2, 12.x before 12.1.3U8, and 12.2.x through 12.5.x before 12.5.9_U2.
When was CVE-2022-26318 disclosed?
CVE-2022-26318 was first published on March 4, 2022, with the most recent update on November 13, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-26318 actively exploited?
Yes. CISA added CVE-2022-26318 to the Known Exploited Vulnerabilities catalog on March 25, 2022, affecting WatchGuard Firebox and XTM Appliances. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation, and watch the vendor's advisory for the fix.
What is the CVSS score of CVE-2022-26318?
CVE-2022-26318 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2022-26318?
CVE-2022-26318 affects WatchGuard Firebox and XTM Appliances.
How do I remediate CVE-2022-26318?
No fix for CVE-2022-26318 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-26318

Explore →

Is Your Infrastructure Affected by CVE-2022-26318?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.