CVE-2025-53139 | Windows Hello Security Feature Bypass Vulnerability

Cleartext transmission of sensitive information in Windows Hello allows an unauthorized attacker to bypass a security feature locally.

Published: 2025-10-14 Last update: 2025-10-23 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-53139 is rated Low Risk (33.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.03%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-53139

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-10-15 — 0.03% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-53139

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.7 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.5 5.2 [email protected]
7.1 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 5.2 [email protected]

Weakness enumeration for CVE-2025-53139

Affected software / configurations for CVE-2025-53139

Vendor Product Version Raw CPE
microsoft windows_10_21h2 < 10.0.19044.6456 cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:*:*
microsoft windows_10_22h2 < 10.0.19045.6456 cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:*:*
microsoft windows_11_22h2 < 10.0.22621.6060 cpe:2.3:o:microsoft:windows_11_22h2:*:*:*:*:*:*:*:*
microsoft windows_11_23h2 <= 10.0.22631.6060 cpe:2.3:o:microsoft:windows_11_23h2:*:*:*:*:*:*:*:*
microsoft windows_11_24h2 < 10.0.26100.6899 cpe:2.3:o:microsoft:windows_11_24h2:*:*:*:*:*:*:*:*
microsoft windows_11_25h2 < 10.0.26200.6899 cpe:2.3:o:microsoft:windows_11_25h2:*:*:*:*:*:*:*:*
microsoft windows_server_2025 <= 10.0.26100.6899 cpe:2.3:o:microsoft:windows_server_2025:*:*:*:*:*:*:*:*

References for CVE-2025-53139

cvelogic Threat Intelligence