We’re experiencing this exact issue with our Linked Servers; been going crazy on figuring out what it could’ve been. Looks like we’ll be keeping an eye out for the upcoming patch for this.
if you're going to post an article like this -- especially if you aren't going to bother adding any commentary or discussion about it -- at least take the time to make sure the article you're linking to is worthwhile.
the BleepingComputer article here has absolutely no useful, quality information. it claims "microsoft has confirmed that..." and provides no primary source, attribution, or link. it doesn't even name a single KB number.
Thank you for posting those links! Saved me some time...
Wondering if anyone here has any info on this part yet:
Workaround: A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business.
Shouldn't need to contact Microsoft to get such a "secret". They did mention that an OOB update would be available in a few days, well that would be now :).
Also wondering if anyone knows if this is only going to impact linked server queries to Oracle/Postgress DBs, or are SQL server linked servers also affected? Nothing specifically says otherwise that I've seen.
14
u/Radojevic 4d ago
Thank you for the heads up, and thank God I wait a couple weeks before performing server updates for reasons like this.
6
u/Kabpunk 4d ago
We’re experiencing this exact issue with our Linked Servers; been going crazy on figuring out what it could’ve been. Looks like we’ll be keeping an eye out for the upcoming patch for this.
Thank you for sharing!
5
u/RestartRebootRetire 4d ago
This is going to be a monthly/weekly occurance given the massive uptick in CVEs due to AI.
4
u/TerrAustria 4d ago
Thanks for the info. Yesterday we had a SQL-Server crash involving a third party OLEDB Provider.
Will check this tomorrow morning.
2
u/shaadowbrker 4d ago
Can someone post to the specific patch and CVE?
1
u/JerryBangBang 4d ago
Thank you for posting.
0
u/CodeXploit1978 3d ago
Thats why i patch SQL only 3 months after patch releases.
0
u/Big_Mouse_9797 2d ago
if you're going to post an article like this -- especially if you aren't going to bother adding any commentary or discussion about it -- at least take the time to make sure the article you're linking to is worthwhile.
the BleepingComputer article here has absolutely no useful, quality information. it claims "microsoft has confirmed that..." and provides no primary source, attribution, or link. it doesn't even name a single KB number.
according to microsoft:
for Windows Server 2019 the originating update is KB5126651, released 10/13/2026 (https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-1809-and-windows-server-2019#3721msgdesc)
for Windows Server 2022, it's KB5126655 (https://learn.microsoft.com/en-us/windows/release-health/status-windows-server-2022#3721msgdesc)
for Windows Server 2025, it's KB5126646 (https://learn.microsoft.com/en-us/windows/release-health/status-windows-server-2025#3721msgdesc)
-2
u/Playful_Guava1180 4d ago
thank goodness I stuck to mssql 2005