[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fzz8UluEAsyFiGtxkDX3gDwYDQP0viMYpCiNHJCzf_08":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":19,"status":27,"created_at":28,"published_at":29,"article":30,"tags":34,"podcasts":47,"controls":48},"aa7004ff-9904-4173-9bfe-715129edc5d0","eol-gms-left-unpatched-as-cisco-and-watchguard-push-critical-fixes","9b737b8f-ab06-4e81-8883-2af95b2b5f86","EoL GMS Left Unpatched as Cisco and WatchGuard Push Critical Fixes","This incident highlights the compounding risk of running End-of-Life (EoL) software in production environments: when vendors cease support, critical vulnerabilities go unaddressed, leaving organizations permanently exposed. SonicWall's decision not to patch two critical flaws in GMS underscores that EoL systems are not just outdated — they are active liabilities. Meanwhile, the Cisco and WatchGuard patches serve as a reminder that timely remediation of critical RCE and authentication vulnerabilities is essential to prevent system compromise. Organizations that delay patching or fail to plan for EoL transitions hand attackers a reliable, indefinite foothold.","**Immediate actions:**\n- Apply Cisco and WatchGuard patches immediately, prioritizing internet-facing and management-plane systems.\n- Identify all instances of SonicWall GMS in your environment and isolate or decommission them until a supported replacement is in place.\n- Restrict network access to unpatched EoL management systems using firewall rules or access control lists.\n\n**Long-term improvements:**\n- Maintain a continuously updated asset inventory that tracks software version, vendor support status, and EoL dates for all network appliances.\n- Establish a formal EoL management policy that triggers migration planning at least 12 months before vendor support ends.\n- Implement a risk-based patch management programme with defined SLAs for critical vulnerabilities (e.g., patch within 24–72 hours for CVSS ≥9.0).\n\n**Detection measures:**\n- Deploy vulnerability scanning tools configured to flag EoL and unpatched components across all network segments on at least a weekly cadence.\n- Monitor management interfaces and authentication logs for anomalous access patterns that may indicate exploitation of unpatched flaws.",[12,13,14,15,16,17,18],"CIS Control 7: Continuous Vulnerability Management","NIST SP 800-53 SI-2: Flaw Remediation","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","OWASP A06:2021 Vulnerable and Outdated Components","NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control","NIS2 Article 21(2)(b)","PCI DSS Requirement 6",{"NIS2 Article 21(2)(b)":20,"PCI DSS Requirement 6":21,"NIST SP 800-53 SI-2: Flaw Remediation":22,"OWASP A06:2021 Vulnerable and Outdated Components":23,"CIS Control 7: Continuous Vulnerability Management":24,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":25,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":26},"NIS2 mandates incident handling and vulnerability management practices, requiring operators of essential services to address known critical vulnerabilities or face regulatory consequences.","PCI DSS Requirement 6 mandates that all system components are protected from known vulnerabilities by installing applicable security patches, making continued use of unpatched EoL GMS non-compliant.","SI-2 requires organizations to identify, report, and correct information system flaws; a formal flaw remediation process would mandate migrating away from EoL GMS rather than leaving critical CVEs unaddressed.","Running EoL SonicWall GMS with known, unpatched critical CVEs is a textbook example of the risk posed by outdated components that no longer receive vendor security fixes.","Regular authenticated scanning would have surfaced the unpatched Cisco, WatchGuard, and EoL SonicWall GMS vulnerabilities, enabling prioritised remediation before attackers could exploit them.","This control requires timely identification and remediation of technical vulnerabilities, including planning for software that will no longer receive security updates from the vendor.","The unpatched authentication flaws in these products directly violate this principle; limiting access to management interfaces reduces exploitability while patches are pending.","published","2026-11-05T13:20:48.940012+00:00","2026-11-05T13:20:48.925+00:00",{"id":7,"url":31,"slug":32,"title":33},"https:\u002F\u002Fwww.securityweek.com\u002Fcisco-watchguard-release-patches-sonicwall-wont-fix-gms-flaws\u002F","cisco-watchguard-release-patches-sonicwall-won-t-fix-gms-flaws-daf3a4","Cisco, WatchGuard Release Patches; SonicWall Won’t Fix GMS Flaws",[35,41],{"id":36,"name":37,"slug":38,"description":39,"color":40},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":42,"name":43,"slug":44,"description":45,"color":46},"af7fce9e-1ce8-4156-93bc-09dcfbfdf29d","Patch Management","patch-management","Unpatched vulnerabilities, delayed updates","#ef4444",[],[49,52,55],{"slug":38,"name":50,"problem":51},"Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":44,"name":53,"problem":54},"Automated patch management","Known holes get closed in days, not months.",{"slug":56,"name":57,"problem":58},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them."]