CVE-2026-43640
Bitwarden Server vulnerability
- Published11 May 2026
Description
Bitwarden Server prior to v2026.4.1 does not require master-password re-authentication when retrieving or rotating an organization's SCIM API key, allowing an authenticated user with SCIM management privileges to obtain the key using only a valid session.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
- https://github.com/bitwarden/server/commit/eb251d9bf80724c87b187661783b9354d1784083
- https://github.com/bitwarden/server/pull/7403
- https://github.com/bitwarden/server/releases/tag/v2026.4.1
- https://sanjokkarki.com.np/blog/bitwarden-scim-key-bypass
- https://www.vulncheck.com/advisories/bitwarden-server-authentication-bypass-via-scim-api-key
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-43640 being actively exploited?
CVE-2026-43640 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.71%.
How severe is CVE-2026-43640?
CVE-2026-43640 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.71% probability of exploitation.
Which products are affected by CVE-2026-43640?
Affected products include Bitwarden Server.
How do I fix CVE-2026-43640?
Upgrade affected software to a fixed version, for example Bitwarden Server 2026.4.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-43640 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.