dbcve.org
365 CopilotApplication · Microsoft

CVE-2025-53799

MEDIUM · 5.5 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.10240.21128 / 10.0.14393.8422 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use of uninitialized resource in Windows Imaging Component allows an unauthorized attacker to disclose information locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a local information disclosure vulnerability in the Windows Imaging Component (WIC), a native Windows API for image processing. The issue involves use of an uninitialized resource, which could allow a local attacker to read sensitive information from memory that was not properly cleared before use.

MitigationApply the relevant Microsoft security update for Windows Imaging Component through Windows Update or patch management systems. As this is a local-only attack requiring no privileges, prioritize patching systems with sensitive data or network exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
365 CopilotApplication
Affected:< 16.0.19220.20000
Windows 10 1507Operating system
Affected:< 10.0.10240.21128
Windows 10 1607Operating system
Affected:< 10.0.14393.8422
Windows 10 1809Operating system
Affected:< 10.0.17763.7792
Windows 10 21h2Operating system
Affected:< 10.0.19044.6332
Windows 10 22h2Operating system
Affected:< 10.0.19045.6332
Windows 11 22h2Operating system
Affected:< 10.0.22621.5909
Windows 11 23h2Operating system
Affected:< 10.0.22631.5909

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Run 'winver' or 'systeminfo' from command prompt, or check HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion in Registry for BuildNumber
    Affected if The installed Windows build number is lower than any of the following: 10240.21128 (Windows 10 1507), 14393.8422 (Windows 10 1607), 17763.7792 (Windows 10 1809), 19044.6332 (Windows 10 21h2), 19045.6332 (Windows 10 22h2), 22621.5909 (Windows 11 22h2), or 22631.5909 (Windows 11 23h2)
  2. Check WIC component file version
    Navigate to %SystemRoot%\System32\wincodec.dll, right-click and select Properties, or run 'powershell (Get-Item C:\Windows\System32\wincodec.dll).VersionInfo'
    Affected if The FileVersion of wincodec.dll is lower than the version bundled with the fixed Windows builds listed above (compare using the Windows build as a proxy)
  3. Check for Microsoft 365 Copilot version (if applicable)
    Open any Copilot-enabled application, go to File > Account, or check installed Office version via 'powershell (Get-Item path-to-office-executable).VersionInfo'
    Affected if Microsoft 365 Copilot is installed and its version is below 16.0.19220.20000

You are affected if your Windows build number or the wincodec.dll version is below the fixed versions for your Windows release, or if you run an affected Microsoft 365 Copilot version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.21128 / 10.0.14393.8422 / 10.0.17763.7792 or later
Fixed in 10.0.10240.2112810.0.14393.842210.0.17763.7792
Interim mitigation

Apply the relevant Microsoft security update for Windows Imaging Component through Windows Update or patch management systems. As this is a local-only attack requiring no privileges, prioritize patching systems with sensitive data or network exposure.

Recommended fix High confidence

Windows 10 version 1507 build 10.0.10240.21128 or later | Windows 10 version 1607 build 10.0.14393.8422 or later | Windows 10 version 1809 build 10.0.17763.7792 or later | Windows 10 version 21h2 build 10.0.19044.6332 or later | Windows 10 version 22h2 build 10.0.19045.6332 or later | Windows 11 ver

  1. Verify current Windows version by running `winver` or `systeminfo` in Command Prompt
  2. For Windows 10/11 systems: Open Settings > Update & Security > Windows Update
  3. Click 'Check for updates' and install all available security updates
  4. Ensure the installed build number meets or exceeds the threshold for your Windows version: Windows 10 1507: 10.0.10240.21128, Windows 10 1607: 10.0.14393.8422, Windows 10 1809: 10.0.17763.7792, Windows 10 21h2: 10.0.19044.6332, Windows 10 22h2: 10.0.19045.6332, Windows 11 22h2: 10.0.22621.5909, Windows 11 23h2: 10.0.22631.5909
  5. For Microsoft 365 Copilot: Update to version 16.0.19220.20000 or later via Office Update or Microsoft 365 admin center
  6. Restart the system after updates are installed
  7. Verify the fix by checking the installed version matches or exceeds the fixed build numbers
Caveat Standard Windows security update - minimal risk; ensure backups and compatibility testing for line-of-business applications before deploying enterprise-wide

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 365 Copilot Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53799 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data