Security readout for executives and security teams
Plain-English summary
AliasVault for Android had a passkey validation flaw that could let a malicious local app request a passkey response for a website it should not access. The issue affects Android versions 0.24.0 through 0.25.2 and is fixed in 0.25.3. This is not listed as actively exploited in KEV.
Executive priority
Treat as a targeted mobile credential risk, not an internet-scale emergency. Patch promptly for users who rely on AliasVault passkeys, especially on managed or high-value devices. Business urgency is moderate because exploitation requires local malicious app presence and user interaction.
Technical view
CVE-2026-22694 is CWE-346 in AliasVault Android’s credential provider. The provider incompletely validated calling app identity, origin, and RP ID for passkey requests. CVSS is 6.1 with local attack vector, low complexity, no privileges, and user interaction required. Fixed in AliasVault Android 0.25.3.
Likely exposure
Organizations are exposed if Android users run AliasVault versions 0.24.0 through 0.25.2 and use passkeys through AliasVault’s credential provider. Exposure depends on a malicious app being present locally and user interaction occurring.
Exploitation context
Sources describe local exploitation under certain conditions by a malicious Android app. No provided source states active exploitation, and the CVE is not in KEV. The primary risk is unauthorized passkey response access, with potential account integrity impact.
Researcher notes
The public record identifies incomplete validation of app identity, origin, and RP ID in the Android credential provider. The patch is linked through PR 1441 and commit b3350473. Public sources do not provide evidence of exploitation in the wild or broader platform impact.
Mitigation direction
- Update AliasVault Android to version 0.25.3 or later.
- Prioritize managed Android devices using AliasVault passkeys.
- Ask users to remove untrusted or unnecessary Android apps.
- Review the GitHub advisory and release notes for vendor guidance.
Validation and detection
- Inventory Android devices with AliasVault installed.
- Confirm installed AliasVault versions are not 0.24.0 through 0.25.2.
- Verify upgrade to AliasVault Android 0.25.3 or later.
- Check mobile management logs for sideloaded or untrusted apps.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-346: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22694 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N1.84.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/aliasvault/aliasvault/security/advisories/GHSA-mvg4-wvjv-332qCVE reference · x_refsource_CONFIRM
- https://github.com/aliasvault/aliasvault/issues/1440CVE reference · x_refsource_MISC
- https://github.com/aliasvault/aliasvault/pull/1441CVE reference · x_refsource_MISC
- https://github.com/aliasvault/aliasvault/commit/b3350473103d6138ab2b63ca130c211717eac67dCVE reference · x_refsource_MISC
- https://github.com/aliasvault/aliasvault/releases/tag/0.25.3CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Origin Validation Error
Origin Validation Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.