Share via

How to fix the vulnerability (CVE-2025-6965)

Sachin Pralhadrao Mangate 50 Reputation points
2025-10-31T07:29:01.09+00:00

Hi Team,

Earlier we got the vulnerability (CVE-2025-6965) regarding the winsqllite3.dll file update. As we have updated the system until the earlier patch released by your side. could you please inform to us how can we mitigate the mentioned vulnerability as file path is part of the OS system directory. Kindly provide the solution for that.

Windows for business | Windows Server | Directory services | Active Directory
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rafael Vargas 20 Reputation points
    2026-01-05T16:54:24.4166667+00:00

    Confirming this is still an issue. Our systems are fully patched as of January 2026, yet the winsqlite3.dll file has not been updated to address CVE-2025-6965.

    Standard patching is not resolving the vulnerability because the binary version remains unchanged in the system directory. We need clarification on whether a specific out-of-band patch is required or if the fix is still pending in the cumulative update stream.

    2 people found this answer helpful.
    0 comments
  2. Sachin Pralhadrao Mangate 50 Reputation points
    2026-01-03T08:36:14.4733333+00:00

    Hi Team,

    Kindly update on this as patching is already completed till the Jan 2026 on system. But still this vulnerability has not been resolved yet.

    1 person found this answer helpful.
    0 comments
  3. andrei.v 0 Reputation points
    2026-03-12T08:27:35.6+00:00

    The vulnerability is fixed in the following KBs:

    For Windows Server 2025 - January 13, 2026—KB5073379

    For Windows Server 2022 - January 13, 2026—KB5073457

    For Windows Server 2019 - extended support for OS - fix KB - January 13, 2026—KB5073723

    Note from KB5073723: You must have installed the August 10, 2021 SSU (KB5005112) before installing this cumulative update.

    For Windows Server 2016 - extended support for OS - fix KB - January 13, 2026—KB5073722

    Note from KB5073722: Until you install the SSU, this update might not be offered to your device … If you are a Windows Server Update Services (WSUS) administrator, you must approve SSU KB5073447 and this update KB5073722.
    0 comments
  4. Jason Nguyen Tran 16,045 Reputation points Independent Advisor
    2025-10-31T08:34:10.4933333+00:00

    Dear Sachin Pralhadrao Mangate,

    The standard and recommended mitigation for a vulnerability in an OS component like this is to apply the official security update. Since you are patched to a previous level, the solution is to install the specific update released for this CVE, which will safely address the binary in-place. Please check the Microsoft Security Update Guide for the June 2025 (or later) cumulative update and deploy it across your environment.

    This cumulative update is the safest and most comprehensive path, as it is tested to properly version and replace the protected OS file without causing system instability. Attempting a manual mitigation could lead to version mismatches and system failures.

    I recommend deploying this update to a test group first for validation before a broader rollout. This should fully resolve the vulnerability reported.

    And if this answer helps resolve your concern, kindly click “Accept Answer” so that others with the same question can benefit too 😊

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.