CVE-2026-61928

Local tampering via cleartext secret storage

Published Aug 11, 2026 · Updated Aug 25, 2026

Cleartext storage in Windows Hello on affected Windows releases allows local users to tamper with sensitive authentication data. Microsoft's published record identifies Windows Hello as storing sensitive information in cleartext, but no public advisory, CVE record reference, or patch note retrieved here discloses the file, registry, or code path that writes the data without protection. Exploitation requires local access with existing authorization on a vulnerable Windows client or server build, and the published scoring bounds the consequence to integrity impact rather than code execution or service interruption.

CVSS severityUnavailable
Unscored
EPSS probability0.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Cleartext storage in Windows Hello on affected Windows releases allows local users to tamper with sensitive authentication data. Microsoft's published record identifies Windows Hello as storing sensitive information in cleartext, but no public advisory, CVE record reference, or patch note retrieved here discloses the file, registry, or code path that writes the data without protection. Exploitation requires local access with existing authorization on a vulnerable Windows client or server build, and the published scoring bounds the consequence to integrity impact rather than code execution or service interruption.

The record

CVE
CVE-2026-61928
Published
Aug 11, 2026
Updated
Aug 25, 2026
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-312
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 11, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 25, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

5.5MicrosoftCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-312Cleartext Storage of Sensitive Information

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo