dbcve.org
Race ConditionWeakness · CWE-362

CVE-2025-0372

MEDIUM · 5.9 CVSS v4.0 Published 2025-05-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated

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
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in HYPR Passwordless on Windows allows Privilege Escalation.This issue affects HYPR Passwordless: before 10.1.

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

A race condition vulnerability exists in HYPR Passwordless for Windows due to improper synchronization when accessing shared resources. This flaw allows an attacker to escalate privileges by exploiting the concurrent execution vulnerability. The issue is present in versions prior to 10.1.

MitigationUpgrade HYPR Passwordless to version 10.1 or later to address the race condition vulnerability.

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

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
High
Privileges
Low
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:A/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Verify HYPR Passwordless is installed
    Open Programs and Features (appwiz.cpl) or check the following registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for an entry named HYPR Passwordless
    Affected if The application is not listed in installed programs, indicating it is not present and therefore not affected
  2. Determine installed version of HYPR Passwordless
    Check the registry key HKLM\SOFTWARE\HYPR\Passwordless\Version or inspect the version property of the main executable (typically in C:\Program Files\HYPR\ or C:\Program Files (x86)\HYPR\) by right-clicking and viewing Properties > Details
    Affected if The displayed version is lower than 10.1 (for example, 10.0.x, 9.x, or earlier)
  3. Check if HYPR service is running
    Open Services (services.msc) and look for a service named HYPR Passwordless or HYPR, or run Get-Service | Where-Object {$_.DisplayName -like '*HYPR*'} via PowerShell
    Affected if The service exists and is running, meaning the vulnerable code is active in memory
  4. Verify Windows version context
    Confirm the operating system is a supported Windows version for HYPR Passwordless by running winver or systeminfo | findstr /B /C:"OS Name"
    Affected if Running a Windows version that supports HYPR Passwordless, as the vulnerability applies specifically to this product on Windows

A system is affected if HYPR Passwordless for Windows is installed with a version number lower than 10.1 and the HYPR service is actively running, exposing the race condition in shared resource synchronization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HYPR Passwordless to version 10.1 or later to address the race condition vulnerability.

Recommended fix Moderate confidence

10.1

  1. 1. Verify current HYPR Passwordless version installed on the Windows system
  2. 2. Download HYPR Passwordless version 10.1 or later from the official HYPR website or trusted distribution channel
  3. 3. Backup any existing HYPR configuration data if applicable
  4. 4. Install version 10.1 following standard installation procedures
  5. 5. Verify the installation completed successfully and the version is now 10.1 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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