SharePoint security fixes released with June 2025 PU and offered through Microsoft Update

Below are the security fixes for the SharePoint OnPrem versions released this month.

SharePoint Server 2016:

  • KB 5002732 – SharePoint Server 2016 (language independent)
  • KB 5002731 – SharePoint Server 2016 (language dependent)

Microsoft Support recommends to install the complete June 2025 CU for SharePoint 2016 rather than individual security fixes.

SharePoint Server 2019:

  • KB 5002729 – SharePoint Server 2019 (language independent)
  • KB 5002727 – SharePoint Server 2019 (language dependent)

Microsoft Support recommends to install the complete June 2025 CU for SharePoint 2019 rather than individual security fixes.

SharePoint Server Subscription Edition:

  • KB 5002736 – SharePoint Server Subscription Edition

This security fix is identical with June 2025 CU for SharePoint Server Subscription Edition.

Office Online Server:

  • KB 5002728 – Office Online Server
Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.

 


Security Vulnerabilities fixed in this PU

Vulnerability SP 2016 SP 2019 SP SE OOS Impact Max Severity
CVE-2025-47163 x x x Remote Code Execution Important
CVE-2025-47165 x Remote Code Execution Important
CVE-2025-47166 x x x Remote Code Execution Important
CVE-2025-47168 x x Remote Code Execution Important
CVE-2025-47169 x x Remote Code Execution Important
CVE-2025-47172 x x x Remote Code Execution Critical
See the Security Update Guide below for more details about the relevant fixes:

3 Comments


  1. Hello,

    I am trying to implement the new hybrid cloud search on a SharePoint SE server.
    This new feature is very poorly documented and extremely difficult to set up.
    The old hybrid search is expected to stop working on 06/30/2025.

    The May 2025 and June 2025 CUs do not allow this new feature to be implemented effectively.

    Do you have any information about the following note found in the June 2025 CU?

    Known issues in this update
    The flight for the new Hybrid Search feature in the Standard release ring was not enabled successfully in the May update, please contact the support team to get the workaround to enable the flight. This issue will be fixed in the July update.

    Do you think the old hybrid search will actually stop working at the end of the month, given that the new “SPOONS” feature cannot yet be implemented?

    Best regards,
    Thank you for your response.

    Reply

  2. Hello,

    I’ve opened a support case with Microsoft, and I was advised to switch to the Early Release version.

    However, when I start the crawl in this mode, I encounter the following errors :

    Ligne 27092: 06/19/2025 09:27:35.49       mssearch.exe (0x3E40)   0x14BC      SharePoint Server Search       Crawler:Gatherer Plugin       4mpjf Warning     The start address https://hybridsearch.xxx.com/sites/test cannot be crawled. Context: Application ‘cloud_hybrid_ssa’, Catalog ‘Portal_Content’ Details: Invalid pointer (0x80004003)   ac4ed0a8-acb9-469b-b0ee-76cc720f2d6b
          
    06/19/2025 09:27:23.42  mssearch.exe (0x3E40)   0x20F8      SharePoint Server Search       Crawler:Azure Plugin       4ktik High     CAzurePlugin::SubmitTaskToSPOONSInternal caught com error 0x80004003 [azurepiobj.cxx:985] src\search\native\gather\plugins\azurepi\azurepiobj.cxx     
    06/19/2025 09:27:23.42  mssearch.exe (0x3E40)   0x20F8      SharePoint Server Search       Crawler:Common       15y3  High     >>>> Exception hr=0x80004003 eip=00007FFF36E6AE3C module=src\search\native\gather\plugins\azurepi\azurepiobj.cxx line=986    
    06/19/2025 09:27:23.42  mssearch.exe (0x3E40)   0x20F8      SharePoint Server Search       Crawler:Azure Plugin       axchc High     CAzurePlugin::SubmitTask caught NLBaseException ComError hr=80004003 [azurepiobj.cxx:731] src\search\native\gather\plugins\azurepi\azurepiobj.cxx

    Are you aware of this issue, or is there any known fix?

    Best regards,
    Thank you for your response.

    Reply

    1. Hi Edmond,
      as you have a support case open I would follow up with the engineer that advised you on the configuration change.
      Cheers,
      Stefan

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.