CVE-2026-65669Patch(microsoft / sql_server_management_studio)

マイクロソフトの定例更新。過去最高の脆弱性974件が修正。Windowsで723件、Officeで222件。ゼロデイはWindows ALPCのCVE-2026-85880とWindows Update StackのCVE-2026-81963。 https://www.securityweek.com/microsoft-patches-record-974-vulnerabilities-including-two-exploited-zero-days/ 要注意なのはCVE-2026-55007（Exchange Serverの任意コード実行（RCE））、CVE-2026-80097​（Authenticatorの権限昇格（EoP））、CVE-2026-69465（SharePointのRCE）、CVE-2026-65669（SQL ServerのEoP）、およびCVE-2026-69525（リモートデスクトップサービスのRCE）等だとZDIの人。

SQL Copilot's Read-Only Mode Wasn't Read-Only. I was in Italy for a month. While I was gone, somebody got sysadmin out of SQL Copilot with a variable. The vulnerability is CVE-2026-65669, the SSMS 22 Copilot bug I wrote about early September. https://www.sqlfingers.com/2026/10/sql-copilots-read-only-mode-wasnt-read.html

Analysis of CVE-2026-65669: privilege escalation through SQL Copilot Read on dbugs: https://dbu.gs/news/analysis-of-cve-2026-65669-privilege-escalation-through-sql-copilot-20261006 Researcher Johann Rehberger disclosed details of CVE-2026-65669 (https://dbu.gs/vulnerability/CVE-2026-65669) — a critical privilege escalation vulnerability in Copilot for SQL Server Management Studio (SSMS). The issue stems from Copilot executing queries with the privileges of the current SQL connection, while its "read-only" mode was enforced by regex-based software validation of queries. The researcher demonstrated that this validation could be bypassed through dynamic invocation of stored procedures: for example, the restriction on "EXEC" could be bypassed by storing the procedure name in a variable and then using "sp_executesql" to execute arbitrary T-SQL. As a result, Copilot could execute "CREATE", "INSERT", "UPDATE", "DELETE", "DROP" and other operations that modify the server state. The researcher also demonstrated an indirect prompt injection: an attacker with fewer privileges placed malicious instructions in database metadata, including through "AGENTS.md" or "CONSTITUTION.md". When a privileged user accessed the object through Copilot, the instructions entered the model's context and triggered a bypass of "read-only", after which arbitrary T-SQL was executed through the victim's connection. In the demonstration, this allowed privileges to be escalated from "db_owner" to the server role "sysadmin". Article: https://embracethered.com/blog/posts/2026/from-select-to-sysadmin-sql-copilot-bluehat-asia/ CVE-2026-65669 — PT-2026-87215: https://dbu.gs/vulnerability/PT-2026-87215

Copilot in SSMS runs SQL as the connected user; its read-only mode was a regex. A db_owner plants instructions in database metadata, a sysadmin uses Copilot, attacker becomes sysadmin. CVE-2026-65669, fixed in 22.8.2. Audit who can write that metadata. https://embracethered.com/blog/posts/2026/from-select-to-sysadmin-sql-copilot-bluehat-asia/

If you use SQL Copilot in SQL Server Management Studio 🔐 Patch this month's update (fixes CVE-2026-65669). Then treat any instructions passed to it as untrusted input, same as a web form because crafted instructions can make it act with your database permissions. https://t.co/ykhbgxxwBt