CVE-2025-59203
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 · uneditedInsertion of sensitive information into log file in Windows StateRepository API 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 confidenceThe Windows StateRepository API improperly writes sensitive information to log files, allowing a local authorized attacker to read this information and gain unauthorized access to potentially sensitive data.
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< 10.0.10240.21161< 10.0.14393.8519< 10.0.17763.7919< 10.0.19044.6456< 10.0.19045.6456< 10.0.22621.6060<= 10.0.22631.6060< 10.0.26100.6899CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check your Windows version against affected buildsOpen Command Prompt and run: `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` or check the registry key `HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion` for the Build NumberAffected 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)
-
Locate StateRepository service log filesCheck the default StateRepository log directory. Typical paths include `%ProgramData%\Microsoft\Windows\StateRepository\logs\` or `C:\ProgramData\Microsoft\Windows\StateRepository\logs\`. Use File Explorer or run: `dir /s /b C:\ProgramData\Microsoft\Windows\StateRepository\*.log`Affected if Log files exist in the StateRepository directory and the Windows version is below the fixed builds listed above
-
Inspect log file contents for sensitive dataOpen any log files found in the StateRepository directory using a text editor or run: `type "C:\ProgramData\Microsoft\Windows\StateRepository\logs\*.log"`. Look for patterns such as: passwords, tokens, API keys, authentication cookies, user credentials, or any PIIAffected if Log files contain any sensitive information such as plain-text credentials, tokens, or personal data that should not be exposed in logs
-
Check StateRepository service executionVerify the StateRepository service is running by opening Services (services.msc) and looking for "StateRepository Service" or run: `sc query StateRepository`Affected if The service is enabled and running, creating logs, on an affected Windows version
You are affected if your Windows build number is below the thresholds AND the StateRepository log files exist and contain sensitive information that should not have been written to logs.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2116110.0.14393.851910.0.17763.7919
Apply the relevant Windows security update (KB) for this CVE when released. Verify that log files in the StateRepository paths do not contain sensitive data.
Install October 2025 cumulative security updates: Windows 10 1507 to build 10.0.10240.21161, Windows 10 1607 to build 10.0.14393.8519, Windows 10 1809 to build 10.0.17763.7919, Windows 10 21h2 to build 10.0.19044.6456, Windows 10 22h2 to build 10.0.19045.6456, Windows 11 22h2 to build 10.0.22621.606
- 1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- 2. Determine which Windows 10 or 11 version and build you are running (e.g., Windows 10 22h2, Windows 11 23h2)
- 3. Navigate to Windows Update: Settings > Update & Security > Windows Update
- 4. Click 'Check for updates' to download and install the latest security updates
- 5. For enterprise environments, deploy the relevant October 2025 cumulative security update (KB5048680 or later) via Windows Server Update Services (WSUS) or Group Policy
- 6. After installation, restart the system to complete the update
- 7. Verify the installed version matches or exceeds the fixed build number for your Windows version (e.g., Windows 10 22h2 should be ≥ 10.0.19045.6456)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59203 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59203 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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