dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-59197

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
Insertion of sensitive information into log file in Windows ETL Channel allows an authorized 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

Windows ETL Channel (Event Tracing for Windows) is writing sensitive information to log files. An authorized local attacker can read these log files to disclose the sensitive data. This is a local information disclosure vulnerability with medium severity due to the requirement for authorized local access.

MitigationReview and configure ETL channel logging settings to prevent sensitive data from being written to log files. Apply any available Microsoft patches for this vulnerability.

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
Windows 10 1507Operating system
Affected:< 10.0.10240.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Check Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the exact Windows build number
    Affected if The build number falls below any of these thresholds: 10240.21161 (1507), 14393.8519 (1607), 17763.7919 (1809), 19044.6456 (21h2), 19045.6456 (22h2), 22621.6060 (11 22h2), 22631.6060 (11 23h2), or 26100.6899 (11 24h2)
  2. Identify ETL log files on the system
    Search for .etl files in common locations such as %SystemRoot%\Tracing, %SystemRoot%\System32\LogFiles, and %ProgramData%\Microsoft\ETLLogs using Get-ChildItem or dir command
    Affected if ETL log files exist in writable directories accessible to local users
  3. Check if ETL tracing sessions are active
    Run 'logman query -ets' in Command Prompt to list active Event Tracing for Windows sessions
    Affected if Active ETL sessions are running and writing to accessible log files
  4. Verify user access to ETL log directories
    Review permissions on directories containing .etl files using icacls or Get-Acl to confirm if standard users can read these files
    Affected if Non-admin users have read access to ETL log directories or files

You are affected if your Windows build number is below the patched versions AND ETL log files with sensitive data are accessible to local users.

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.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Review and configure ETL channel logging settings to prevent sensitive data from being written to log files. Apply any available Microsoft patches for this vulnerability.

Recommended fix High confidence

Install the appropriate Windows cumulative security update for your specific Windows version (10.0.xxxx build) from Windows Update or Microsoft Update Catalog

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Determine which Windows 10 or 11 version and build you are running from the affected list
  3. Apply the appropriate Windows Security Update for your version - these are cumulative updates that include the fix for CVE-2025-59197
  4. For Windows 10 1507: Update to build 10.0.10240.21161 or later
  5. For Windows 10 1607: Update to build 10.0.14393.8519 or later
  6. For Windows 10 1809: Update to build 10.0.17763.7919 or later
  7. For Windows 10 21h2: Update to build 10.0.19044.6456 or later
  8. For Windows 10 22h2: Update to build 10.0.19045.6456 or later
Caveat Standard Windows cumulative update - review release notes for any known issues specific to your environment before deploying

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59197 — 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-59197 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