{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-22694 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22694 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22694 is a medium-severity vulnerability in aliasvault, published on 14 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-22694 and fix it if it is affected.\n\nWhat it is: CVE-2026-22694 is a medium-severity vulnerability in aliasvault, published on 14 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-22694 in the wild and no public exploit code.\n\nAffected product: aliasvault. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-22694/ (Markdown: https://insights.sbomify.com/CVE-2026-22694/index.md)","id":"CVE-2026-22694","markdown":"https://insights.sbomify.com/CVE-2026-22694/index.md","name":"CVE-2026-22694","record":{"aliases":["GHSA-mvg4-wvjv-332q"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android password manager","requires_auth":"none","summary":"A malicious Android app can bypass passkey origin validation to obtain credentials for unauthorized sites in AliasVault.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"aliasvault","vendor":"aliasvault"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"AliasVault is a privacy-first password manager with built-in email aliasing. AliasVault Android versions 0.24.0 through 0.25.2 contained an issue in how passkey requests from Android apps were validated. Under certain local conditions, a malicious app could attempt to obtain a passkey response for a site it was not authorized to access. The issue involved incomplete validation of calling app identity, origin, and RP ID in the Android credential provider. This issue was fixed in AliasVault Android 0.25.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"AliasVault is Missing Origin Validation in Android Passkey Credential Provider","id":"CVE-2026-22694","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"LIBPNG has a heap buffer over-read in png_image_read_direct_scaled (regression from CVE-2025-65018 fix)","id":"CVE-2026-22695"},"packages":[],"prev":{"headline":"Null Pointer Dereference in SubtableUnicodesCache::create leading to DoS","id":"CVE-2026-22693"},"products":["aliasvault"],"published":"2026-01-14","related":[{"cvss_score":9.3,"headline":"AliasVault affected by Cross-Site Scripting (XSS) via Email HTML Rendering","id":"CVE-2026-26266","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":2,"headline":"AliasVault App Backup aliasvault.xml backup","id":"CVE-2026-2974","kev_date_added":null,"published":"2026-02-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-14","vendors":["aliasvault"]},"summary":"A malicious Android app can bypass passkey origin validation to obtain credentials for unauthorized sites in AliasVault.","url":"https://insights.sbomify.com/CVE-2026-22694/"}