{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31835 exists.","fix":"No fix has been published for CVE-2026-31835 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-31835 is a medium-severity vulnerability in dani-garcia vaultwarden, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-31835 and fix it if it is affected.\n\nWhat it is: CVE-2026-31835 is a medium-severity vulnerability in dani-garcia vaultwarden, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31835 exists.\n\nAffected product: dani-garcia vaultwarden. 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-31835/ (Markdown: https://insights.sbomify.com/CVE-2026-31835/index.md)","id":"CVE-2026-31835","markdown":"https://insights.sbomify.com/CVE-2026-31835/index.md","name":"CVE-2026-31835","record":{"aliases":["GHSA-x7g7-cgx5-jhx2"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Vaultwarden server","requires_auth":"low_privilege","summary":"Attackers can permanently disable WebAuthn two-factor authentication for users by tampering with credential metadata before signature verification occurs.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vaultwarden","vendor":"dani-garcia"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Vaultwarden is a Bitwarden-compatible server written in Rust. In versions 1.35.4 and earlier, the WebAuthn authentication flow in `validate_webauthn_login()` updates persistent credential metadata (1backup_eligible1 and 1backup_state flags1) based on unverified `authenticatorData` before signature validation is performed. An attacker who knows a user's password but cannot produce a valid WebAuthn signature can permanently modify the stored backup flags for that user's credential. If signature verification fails, the database update is not rolled back. This can result in a persistent denial of service of WebAuthn two-factor authentication for affected credentials. This issue has been fixed in version 1.35.5.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Vaultwarden WebAuthn credential metadata tampered before signature verification","id":"CVE-2026-31835","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Mass Assignment Privilege Escalation in Checkmate","id":"CVE-2026-31836"},"packages":[],"prev":{"headline":"Umbraco Affected by Vertical Privilege Escalation via Missing Authorization Checks","id":"CVE-2026-31834"},"products":["vaultwarden"],"published":"2026-05-05","related":[{"cvss_score":9.8,"headline":"Vaultwarden vulnerable to user impersonation","id":"CVE-2024-55225","kev_date_added":null,"published":"2025-01-09"},{"cvss_score":9.6,"headline":"Vaultwarden HTML injection vulnerability","id":"CVE-2024-55224","kev_date_added":null,"published":"2025-01-09"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2024-39924","kev_date_added":null,"published":"2024-09-13"},{"cvss_score":8.7,"headline":"Vaultwarden: Cross-Org Group Binding Enables Unauthorized Read And Write Access Into Another Organization","id":"CVE-2026-43912","kev_date_added":null,"published":"2026-05-11"},{"cvss_score":8.3,"headline":"Vaultwarden: Privilege Escalation via Bulk Permission Update to Unauthorized Collections by Manager","id":"CVE-2026-27802","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":8.3,"headline":"Vaultwarden: Collection Management Operations Allowed Without `manage` Verification for Manager Role","id":"CVE-2026-27803","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":8.1,"headline":"Vaultwarden: Unconfirmed Owner Can Purge Entire Organization Vault","id":"CVE-2026-43913","kev_date_added":null,"published":"2026-05-11"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-06","vendors":["dani-garcia"]},"summary":"Attackers can permanently disable WebAuthn two-factor authentication for users by tampering with credential metadata before signature verification occurs.","url":"https://insights.sbomify.com/CVE-2026-31835/"}