[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$feMNZgfJjl8s9AOjBNq9tkapJ4S73xd99719dNQG0GYE":3},{"article":4,"iocs":38,"watch_terms":39,"solutions":40,"lesson":104},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":30,"category":31,"article_tags":35},"c0acfde0-b471-4792-9324-6d311f3fd717","Microsoft: Recent Windows updates cause SQL Server performance issues","microsoft-recent-windows-updates-cause-sql-server-performance-issues-52b2d8","Microsoft has confirmed that Windows updates released since the October 2026 Patch Tuesday are causing SQL Server performance and stability issues. [...]","Microsoft has confirmed that Windows updates released since the October 2026 Patch Tuesday are causing performance and stability issues for SQL Server. The problem stems from server queries that leave connections open after completion, leading to an accumulation of connections that degrade server performance. This issue affects SQL Server linked server queries using OLE DB providers to connect to external databases like Oracle and PostgreSQL.","Microsoft confirms Windows updates since Oct 2026 cause SQL Server performance issues.","https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fmicrosoft\u002Fmicrosoft-recent-windows-updates-cause-sql-server-performance-issues\u002F","https:\u002F\u002Fwww.bleepstatic.com\u002Fcontent\u002Fhl-images\u002F2026\u002F10\u002F21\u002FWindows_headpic.jpg","2026-11-12T12:11:11+00:00","2026-11-12T13:00:11.623356+00:00",7,[17,20,22,24,26,28],{"name":18,"type":19},"SQL Server","product",{"name":21,"type":19},"Windows 10",{"name":23,"type":19},"Windows 11",{"name":25,"type":19},"Windows Server 2012",{"name":27,"type":19},"Oracle",{"name":29,"type":19},"PostgreSQL","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":30,"icon":32,"name":33,"slug":34},null,"Vulnerabilities","vulnerabilities",[36],{"category":37},{"id":30,"icon":32,"name":33,"slug":34},[],[18,21,23],{"controls":41,"vendors":96},[42,71],{"slug":43,"name":44,"problem":45,"products":46},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[47,55,63],{"vendor_slug":48,"vendor_name":49,"vendor_logo":50,"product_slug":51,"product_name":52,"url":53,"description":54},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","vmdr","Qualys VMDR","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fvulnerability-management-detection-response\u002F","Vulnerability management, detection and response with risk-based prioritisation.",{"vendor_slug":56,"vendor_name":57,"vendor_logo":58,"product_slug":59,"product_name":60,"url":61,"description":62},"rapid7","Rapid7","\u002Fvendor-logos\u002Frapid7.png","insightvm","Rapid7 Exposure Command (InsightVM)","https:\u002F\u002Fwww.rapid7.com\u002Fproducts\u002Finsightvm\u002F","Vulnerability scanning and risk-based prioritisation; InsightVM is now part of Exposure Command, alongside attack surface and cloud risk.",{"vendor_slug":64,"vendor_name":65,"vendor_logo":66,"product_slug":67,"product_name":68,"url":69,"description":70},"holm-security","Holm Security","\u002Fvendor-logos\u002Fholm-security.png","holm-security-platform","Holm Security Platform","https:\u002F\u002Fwww.holmsecurity.com\u002F","Vulnerability scanning of systems, web applications, cloud and the external attack surface, plus phishing simulation.",{"slug":72,"name":73,"problem":74,"products":75},"patch-management","Automated patch management","Known holes get closed in days, not months.",[76,84,88],{"vendor_slug":77,"vendor_name":78,"vendor_logo":79,"product_slug":80,"product_name":81,"url":82,"description":83},"ninjaone","NinjaOne","\u002Fvendor-logos\u002Fninjaone.png","ninjaone-patch-management","NinjaOne Patch Management","https:\u002F\u002Fwww.ninjaone.com\u002Fpatch-management\u002F","Automated patching of operating systems and third-party applications from the cloud.",{"vendor_slug":48,"vendor_name":49,"vendor_logo":50,"product_slug":72,"product_name":85,"url":86,"description":87},"Qualys Patch Management","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fpatch-management\u002F","Patch deployment for operating systems and third-party applications, linked to vulnerability findings.",{"vendor_slug":89,"vendor_name":90,"vendor_logo":91,"product_slug":92,"product_name":93,"url":94,"description":95},"manageengine","ManageEngine","\u002Fvendor-logos\u002Fmanageengine.png","patch-manager-plus","ManageEngine Patch Manager Plus","https:\u002F\u002Fwww.manageengine.com\u002Fpatch-management\u002F","Patch management for operating systems and third-party applications, on premises or in the cloud.",[97],{"slug":98,"name":99,"logo_path":100,"roles":101},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png",[102,103],"reported_by","affected",{"slug":105,"title":106,"body":107,"framework_refs":108,"framework_notes":114},"windows-patch-causes-sql-server-connection-leak-and-performance-degradation","Windows Patch Causes SQL Server Connection Leak and Performance Degradation","Microsoft's October 2026 Patch Tuesday updates introduced a regression that causes SQL Server linked server queries to leave database connections open after completion, gradually exhausting connection pools and degrading server performance. This highlights a critical risk in patch management: even vendor-supplied updates from trusted sources can introduce unintended instability in complex, interdependent enterprise environments. Organizations relying on SQL Server linked queries to Oracle, PostgreSQL, or other external databases faced potential outages without warning. It matters because patch-induced regressions can be just as disruptive as the vulnerabilities the patches were meant to fix, and without proper testing pipelines or rollback plans, recovery is slow and painful.",[109,110,111,112,113],"CIS Control 7: Continuous Vulnerability Management (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 DE.CM-01: Continuous Monitoring","NIS2 Article 21(2)(b)","NIS2 Article 21(2)(e)",{"NIS2 Article 21(2)(b)":115,"NIS2 Article 21(2)(e)":116,"NIST SP 800-53 SI-2: Flaw Remediation":117,"NIST CSF 2.0 DE.CM-01: Continuous Monitoring":118,"CIS Control 7: Continuous Vulnerability Management (v8)":119},"NIS2 Article 21(2)(b) covers incident handling procedures, and having a documented response plan for patch-induced regressions — including rollback steps — would have reduced the time SQL Server environments spent in a degraded state.","This point requires security measures in system maintenance including vulnerability and patch handling, directly applicable to the need for structured patch validation processes that would catch vendor-introduced regressions before production deployment.","SI-2 requires organizations to test software updates before installation, a step that would have revealed the connection-leak regression introduced by this Windows patch in a non-production environment first.","This category calls for continuous monitoring of system performance and security events, which would have surfaced the abnormal accumulation of open SQL Server connections shortly after the patch was applied.","CIS Control 7 requires organizations to evaluate and remediate software changes — including vendor patches — in a planned, risk-aware manner, which would have prompted staged testing that caught this regression before production impact."]