Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.new Create a CVE report
Check your stack
CVE-2026-55587high8.1

AliasVault: Browser extension WebAuthn bridge accepts forged origin/RP ID

Impact

The AliasVault browser extension, prior to version 0.29.4, accepts forged origin and relying-party identifiers, allowing a malicious website to obtain a valid assertion for a different website if a victim with a matching stored passkey approves the prompt. The extension must be installed, unlocked, and configured as a passkey provider. A stored passkey for the impersonated site is required.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.
Applies when

Exploitation requires the extension to be installed, unlocked, and configured as a passkey provider, requires a stored passkey for the impersonated site, and cannot occur silently because the victim must approve the prompt.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

aliasvault · GitHub_M

aliasvault

1 range
GitHub_M version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

< 0.29.4

unaffected

unknown

Other versions: unknown

Original source description

AliasVault is a privacy-first password manager with built-in email aliasing. Prior to 0.29.4, the AliasVault browser extension passkey provider does not bind passkey requests to the actual webpage origin or verify that the requested relying-party identifier matches the current website. A malicious website can provide forged origin and relying-party values and, if a victim with a matching stored passkey approves the AliasVault passkey prompt, obtain a valid assertion for a different website. Exploitation requires the extension to be installed, unlocked, and configured as a passkey provider, requires a stored passkey for the impersonated site, and cannot occur silently because the victim must approve the prompt. The server, web application, and mobile applications are not affected. This issue is fixed in version 0.29.4.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-55587

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-346 ↗

CWE-346: Origin Validation Error

GitHub_M

Related →
Contributing organizations · 2
GitHub_M

Assigning organization

2026-10-15
CISA-ADP

Additional data publisher

2026-10-28

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

3 sources
github.com/aliasvault/aliasvault/security/advisories/GHSA-f99p-jfhr-6ffc
Security advisoryGitHub_M
github.com/aliasvault/aliasvault/commit/a60d0966e66ecf4f6558dc40e3feb1313072ce2b
PatchGitHub_M
github.com/aliasvault/aliasvault/releases/tag/0.29.4
Release notesGitHub_M