dbcve.org
Link Following (Symlink)Weakness · CWE-59

CVE-2025-2102

MEDIUM · 5.7 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 →
57/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
Improper Link Resolution Before File Access ('Link Following') 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

Improper Link Resolution Before File Access (link following) vulnerability in HYPR Passwordless on Windows allows a local attacker to manipulate file access through symbolic links, potentially escalating privileges. The application fails to properly validate file paths before accessing them.

MitigationUpgrade HYPR Passwordless to version 10.1 or later to remediate this 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
High
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:A/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N/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. Confirm HYPR Passwordless is installed
    Open Programs and Features (appwiz.cpl) or check for HYPR Passwordless in the Windows installation directory, typically under Program Files or Program Files (x86).
    Affected if HYPR Passwordless is present on the system
  2. Identify installed HYPR Passwordless version
    Right-click the main HYPR executable (commonly hypr.exe or similar), select Properties, and view the File Version tab. Alternatively, check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for the installed version string.
    Affected if The version displayed is lower than 10.1.0
  3. Verify symbolic link handling configuration
    Review HYPR Passwordless configuration files for settings related to file path validation or link resolution. Check installation directory for config files (.json, .xml, .ini) that may control file access behavior.
    Affected if File path validation is disabled or not present in configuration

The environment is affected if HYPR Passwordless is installed with a version lower than 10.1 and the application uses file access operations that could follow symbolic links.

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 remediate this vulnerability.

Recommended fix Moderate confidence

10.1

  1. Obtain HYPR Passwordless version 10.1 or later from the official HYPR source at hypr.com
  2. Back up any existing HYPR Passwordless configuration data before upgrading
  3. Install or upgrade to HYPR Passwordless version 10.1
  4. Verify the installation completed successfully and the version is correct

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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