dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-4522

MEDIUM · 6.7 CVSS v4.0 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
8 weeks old

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
Missing authentication for critical function vulnerability in HYPR Passwordless on Windows allows Credentials Interception. This issue affects HYPR Passwordless: before 11.1.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

HYPR Passwordless on Windows versions prior to 11.1.1 lack authentication checks on a critical function, enabling unauthenticated attackers to intercept credentials. This is a broken authentication vulnerability where the application fails to verify the caller's identity before allowing access to sensitive credential-handling operations.

MitigationUpgrade HYPR Passwordless to version 11.1.1 or later to implement proper authentication on the affected critical function.

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

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/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. Verify HYPR Passwordless is installed
    Open Windows Settings > Apps & Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*HYPR*'}' in PowerShell to list installed HYPR products
    Affected if HYPR Passwordless appears in the installed programs list
  2. Determine the installed version
    Locate the HYPR Passwordless installation directory (typically C:\Program Files\HYPR or C:\Program Files (x86)\HYPR) and check the version information in the executable properties, or use 'Get-ItemProperty' on the uninstall registry entry for the DisplayVersion field
    Affected if The displayed version is a version number lower than 11.1.1 (e.g., 11.0.0, 10.x.x)
  3. Compare version against the affected range
    Parse the version number found and compare it numerically to 11.1.1 - any version prior to 11.1.1 (including 11.0.x, 10.x, and earlier) falls within the affected range
    Affected if The installed version is less than 11.1.1 when compared semantically
  4. Confirm the credential handling component is active
    Check if the HYPR Passwordless service is running (via Services.msc or 'Get-Service HYPR*') and verify the application is configured to handle passwords or credentials for Windows login or applications
    Affected if The HYPR Passwordless service is running and the application manages credentials for authentication

If HYPR Passwordless is installed with a version lower than 11.1.1 and the credential-handling service is active, the environment is affected by CVE-2026-4522.

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 11.1.1 or later to implement proper authentication on the affected critical function.

Recommended fix High confidence

Upgrade to HYPR Passwordless version 11.1.1 or later

  1. 1. Verify current installed version of HYPR Passwordless on the Windows system (check via Programs and Features or the HYPR application itself)
  2. 2. Download HYPR Passwordless version 11.1.1 or later from the official HYPR website (www.hypr.com) or your organization's approved software distribution point
  3. 3. Create a backup of any local HYPR configuration data if feasible, though credentials are typically stored server-side
  4. 4. Run the installer for the new version and complete the upgrade following standard installation prompts
  5. 5. Verify the installation was successful by checking the version number in the application or Programs and Features
  6. 6. Test that HYPR Passwordless authentication is functioning normally

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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