SQL Server 2025 Cumulative Update 5 (KB5084896) is now listed with build 17.0.4045.5. Microsoft says the update includes seven fixes after Cumulative Update 4 and updates both the SQL Server engine and Analysis Services components.

For DBAs and developers, the release is notable not just for the fix count, but for a mix of engine changes, platform-specific corrections, and component updates that touch setup, memory management, full-text search, Integration Services, CLR spatial procedures, and Linux replication.

Improvements and fixes

CU5 contains 7 verified fixes. The changes are spread across several areas:

  • SQL Server Engine / Memory Management: adds a new max lock manager cache memory (%) configuration setting to control the maximum size of lock manager cache memory.
  • SQL Server Engine / In-Memory OLTP: addresses CPU starvation during garbage collection scans of hash indexes by adding yields at regular intervals.
  • SQL Server Engine / Search: enables the FulltextIndexVersion2 feature through the fulltext_index_version database-scoped configuration and fixes an issue where full-text indexing of .docx files could return incorrect results in a specific hyperlink-related paragraph layout.
  • SQL Server Engine / SQL System CLR Types: fixes a SQL injection issue involving the sp_help_spatial_geography_index and sp_help_spatial_geometry_index stored procedures.
  • SQL Setup / Windows: fixes an EntryPointNotFoundException for GetNumaNodeProcessorMask2 that could occur during setup on older Windows versions.
  • Integration Services / Windows: addresses an XML External Entity (XXE) issue in the Web Service Task by blocking the file:// protocol in WSDL service endpoints.
  • SQL Server Engine / Linux Replication: adds support for configuring change feed parameters through mssql.conf.

Analysis Services is also updated as part of this release, with Microsoft listing product version 17.0.25.223 and file version 2025.170.25.223.

Known issues

Microsoft lists two known issues with CU5:

  • SESSION_CONTEXT in parallel plans: queries that use SESSION_CONTEXT can return incorrect results or generate access violation dump files when they run in parallel query plans, especially when the session is reset for reuse.
  • Linked server queries using MSDASQL: linked server queries that use the MSDASQL provider and specify a provider string (@provstr) can fail with error 7416, stating that access to the remote server is denied because no login-mapping exists.

Microsoft also notes that removal of a known issue from the source would not, by itself, prove resolution.

Release details

  • KB: KB5084896
  • Update: Cumulative Update 5 for Microsoft SQL Server 2025
  • Build: 17.0.4045.5
  • Official release date: 2026-05-20

Official source