KB5126149 cause SnowFlakeID broken in MS SQL Server

Water Yue 0 Reputation points
2026-09-18T08:22:44.49+00:00

Below windows update package caused SnowFlakeID broken in MS SQL SERVER, this issue is very serious, caused all transactions cannot record, below are the KB and mapping windows version:

OS .NET Update KB Vulnerabilities Addressed
Win11 24H2 / 25H2 / Windows Server 2025 KB5126052 CVE-2026-62886, CVE-2026-69522
Windows Server 2022 KB5126149 CVE-2026-62886, CVE-2026-69522
Windows Server 2019 KB5126144 (Rollup) CVE-2026-62886, CVE-2026-69522

Here is the part of SnowFlakeID create script: `Create Assembly "System.Threading" from @SystemThreading WITH PERMISSION_SET = UNSAFE;

Create Assembly "System.Runtime.Extensions" from @SystemRuntimeExtensions
WITH PERMISSION_SET = UNSAFE;


Create Assembly "System.Diagnostics.Debug" from @SystemDiagnosticsDebug
WITH PERMISSION_SET = UNSAFE;


Create Assembly "System.Runtime" from @SystemRuntime
WITH PERMISSION_SET = UNSAFE;


CREATE ASSEMBLY [IdGen]
FROM .........
WITH PERMISSION_SET = UNSAFE;



CREATE ASSEMBLY [SnowFlakeID]
FROM ...
WITH PERMISSION_SET = UNSAFE;
END;

EXECUTE('CREATE FUNCTION GetSFIDFromDll(@inputOne int)
RETURNS [bigint] WITH EXECUTE AS CALLER, RETURNS NULL ON NULL INPUT
AS
EXTERNAL NAME [SnowFlakeID].[IdGenerator.SnowFlakeID].[GenerateID]');

IF NOT EXISTS (SELECT * FROM sys.objects WHERE name = 'fn_GetPKID' AND TYPE = 'FN')
BEGIN
EXECUTE('CREATE FUNCTION fn_GetPKID() RETURNS BIGINT
AS
BEGIN
DECLARE @nodeID nvarchar(100);
DECLARE @snowFlakeID BIGINT;
SELECT @nodeID = Value FROM T_NODE_INFO WHERE Name=''NodeID''
SELECT @snowFlakeID = dbo.GetSFIDFromDll(CAST(@nodeID as int))
RETURN @snowFlakeID
END')
END;`
SQL Server | SQL Server Transact-SQL
0 comments No comments

1 answer

Sort by: Oldest
  1. Erland Sommarskog 137.4K Reputation points MVP Volunteer Moderator
    2026-09-18T10:49:39.0633333+00:00

    I am not at all familiar with this "SnowFlakeID". Is this is something that is supplied by Microsoft?

    Seeing which assemblies you add to SQL Server, I ask myself: Are those actually supported? (Just because SQL Server permits them to be loaded, does not have to mean that they are actually supported.)

    In any case, if this is an issue that is blocking you, the only way to get a resolution is to open a support case.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.