CVE-2026-55587: aliasvault · Origin Validation Error
Affects aliasvaultSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 0.29.4 soon.
Data as of 28 Oct 2026, 20:29 UTC
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-28.
- Patch
- Available – fixed in 0.29.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade aliasvault and aliasvault/aliasvault to 0.29.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| aliasvaultaliasvault | Affected
| Fixed in
|
GitHubaliasvault/aliasvaultpkg:github/aliasvault/aliasvaultOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should update the AliasVault browser extension to version 0.29.4 or later, where this origin validation issue is fixed. Since the vulnerability requires user approval of the passkey prompt, educating users to be cautious about unexpected passkey requests can also help mitigate risk. No other action is required as the vulnerability is patched.
Description
AliasVault browser extension versions prior to 0.29.4 have a vulnerability where passkey requests are not properly bound to the actual webpage origin or verified against the relying-party identifier. This allows a malicious website to forge these values and, with user approval, obtain a valid passkey assertion for a different site. Exploitation requires the extension to be installed, unlocked, configured as a passkey provider, and the victim to have a stored passkey for the impersonated site. The issue is fixed in version 0.29.4.