{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43911 exists.","fix":"No fix has been published for CVE-2026-43911 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-43911 is a medium-severity vulnerability in dani-garcia vaultwarden, published on 11 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-43911 and fix it if it is affected.\n\nWhat it is: CVE-2026-43911 is a medium-severity vulnerability in dani-garcia vaultwarden, published on 11 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-43911 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-43911/ (Markdown: https://insights.sbomify.com/CVE-2026-43911/index.md)","id":"CVE-2026-43911","markdown":"https://insights.sbomify.com/CVE-2026-43911/index.md","name":"CVE-2026-43911","record":{"aliases":["GHSA-6j4w-g4jh-xjfx"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Password manager server","requires_auth":"low_privilege","summary":"Attackers can maintain session access using old refresh tokens after security-sensitive operations like password changes, bypassing intended session invalidation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vaultwarden","vendor":"dani-garcia"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"Vaultwarden is a Bitwarden-compatible server written in Rust. Prior to 1.35.5, refresh tokens are not invalidated when the user's security_stamp is rotated by some security-sensitive operations (password change, KDF change, key rotation, email change, org admin password reset, emergency access takeover). This allows an attacker holding a previously obtained refresh token to maintain session access even after the user has taken action to secure their account. This vulnerability is fixed in 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: Refresh tokens not invalidated on security stamp rotation","id":"CVE-2026-43911","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Vaultwarden: Cross-Org Group Binding Enables Unauthorized Read And Write Access Into Another Organization","id":"CVE-2026-43912"},"packages":[],"prev":{"headline":"Appium java-client Allows Network Pivot via Unvalidated directConnect Redirect in AppiumCommandExecutor","id":"CVE-2026-43910"},"products":["vaultwarden"],"published":"2026-05-11","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":"total"},"state":"PUBLISHED","updated":"2026-05-12","vendors":["dani-garcia"]},"summary":"Attackers can maintain session access using old refresh tokens after security-sensitive operations like password changes, bypassing intended session invalidation.","url":"https://insights.sbomify.com/CVE-2026-43911/"}