PatchSiren cyber security CVE debrief
CVE-2026-15468 HYPR CVE debrief
A vulnerability in HYPR Passwordless on Windows allows for privilege escalation due to an authorization bypass through a user-controlled key. This issue affects HYPR Passwordless versions before 11.3.3. The vulnerability could be used to bypass authorization mechanisms, potentially leading to unauthorized actions. Defenders responsible for HYPR Passwordless deployments on Windows should assess the potential impact of this vulnerability and prioritize verification and mitigation efforts. The CVE record and source item provide details on the vulnerability, its impact, and the affected versions of HYPR Passwordless.
- Vendor
- HYPR
- Product
- Passwordless
- CVSS
- MEDIUM 6.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-13
- Original CVE updated
- 2026-10-14
- Advisory published
- 2026-10-13
- Advisory updated
- 2026-10-14
Who should care
Defenders responsible for HYPR Passwordless deployments on Windows should assess the potential impact of this vulnerability and prioritize verification and mitigation efforts.
Why it matters
Defenders should prioritize verifying the version of HYPR Passwordless in use and assessing the potential impact of privilege escalation within their environment.
- Privilege escalation could lead to increased access and control within the environment.
- The vulnerability could be used to bypass authorization mechanisms, potentially leading to unauthorized actions.
Technical summary
The vulnerability in HYPR Passwordless on Windows allows for privilege escalation due to an authorization bypass through a user-controlled key. This issue affects HYPR Passwordless versions before 11.3.3. The vulnerability could be used to bypass authorization mechanisms, potentially leading to unauthorized actions. Defenders should prioritize verifying the version of HYPR Passwordless in use and assessing the potential impact of privilege escalation within their environment.
Defensive priority
Defenders should prioritize verifying the version of HYPR Passwordless in use and assessing the potential impact of privilege escalation within their environment.
Recommended defensive actions
- Verify the version of HYPR Passwordless in use and ensure it is 11.3.3 or later.
- Assess the potential impact of privilege escalation within the environment.
- Implement compensating controls to mitigate the vulnerability.
Evidence notes
The CVE record and source item provide details on the vulnerability, its impact, and the affected versions of HYPR Passwordless. The vulnerability in HYPR Passwordless on Windows allows for privilege escalation due to an authorization bypass through a user-controlled key. This issue affects HYPR Passwordless versions before 11.3.3. The source item and CVE record provide information on the affected versions and the potential impact of the vulnerability. Defenders should verify the patch
Sources and references
Verified primary and authoritative sources
-
CVE-2026-15468 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-15468
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-15468 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-15468
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
CVE-2026-15468
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/15xxx/CVE-2026-15468.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://www.hypr.com/trust-center/security-advisories
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.