Skip to main content

Bitwarden Server CVE-2026-43639

| EUVDEUVD-2026-29170 HIGH
Missing Authorization (CWE-862)
2026-05-11 VulnCheck GHSA-79fq-fw2p-vq3j
8.9
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Compromise provider service user credentials
  2. Delivery
    Enumerate target organization IDs
  3. Exploit
    Send crafted POST to /providers/{providerId}/clients/existing
  4. Install
    Bypass authorization check
  5. C2
    Add victim org to attacker's provider
  6. Execute
    Gain admin access to victim vault
  7. Impact
    Exfiltrate credentials and secrets

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires valid provider service user credentials on Bitwarden Server Cloud platform. The attacker must have authenticated access with provider service user role (not regular user or even organization admin) and knowledge of target organization IDs to specify in API requests. This is a Cloud-only vulnerability - self-hosted Bitwarden Server installations are protected by the SelfHosted(NotSelfHostedOnly = true) endpoint restriction which blocks access to POST /providers/{providerId}/clients/existing entirely. Default Cloud configurations running vulnerable versions (pre-v2026.4.0) are exploitable without additional feature enablement. Attack complexity is rated 'high' but primarily reflects the prerequisite of obtaining provider service user credentials rather than technical exploit difficulty. No user interaction is required once the attacker has valid credentials (UI:N). The provider service user role limits the attack surface compared to vulnerabilities exploitable by any authenticated user, but MSP account compromise is a realistic threat vector in managed service environments.

Impact

Real-world risk is HIGH despite attack complexity indicators suggesting otherwise. CVSS 8.9 with AV:N/AC:H/PR:H reflects network-accessible attack requiring high privileges and high complexity, but the 'high complexity' is misleading - exploitation simply requires valid provider service user credentials and knowledge of target organization IDs. The PR:H (high privileges required) is accurately scored, as attackers need authenticated provider service user access, not just regular user credentials. Publicly available exploit code significantly lowers the technical barrier for threat actors who have compromised provider accounts. The impact is severe: complete organization takeover grants attackers access to all stored credentials, secrets, and sensitive data for the hijacked organization, plus administrative control to exfiltrate, modify, or destroy vault contents. While no CISA KEV listing exists suggesting targeted exploitation campaigns, the authentication bypass tag and cloud-only scope indicate this affects organizations using Bitwarden's Cloud MSP features. The narrow attack surface (provider service users only, Cloud platform only) somewhat limits exposure, but MSP credential compromise is an established attacker tactic. Vendor-released patch v2026.4.0 is available and deployment is urgent for Cloud customers utilizing provider features.

Exploit ScenarioDerived

An attacker compromises valid provider service user credentials through phishing, credential stuffing, or insider threat. Using these authenticated credentials and the publicly documented exploit technique from Sanjok Karki's writeup, the attacker crafts a POST request to /providers/{providerId}/clients/existing with the organization ID of a target company they wish to hijack. The missing authorization check allows the request to succeed, adding the victim organization to the attacker's provider scope. The attacker now has full administrative access to the victim organization's Bitwarden vault, enabling credential exfiltration, secrets theft, or deployment of backdoors across the victim's infrastructure by compromising stored administrative passwords.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 11, 2026

Provider service users in Bitwarden Server Cloud can hijack arbitrary organizations via unauthorized API endpoint access, achieving complete administrative takeover. The vulnerability exploits a missing authorization check in the POST /providers/{providerId}/clients/existing endpoint, allowing authenticated provider users to add any organization to their provider without the target's consent. Publicly available exploit code exists (detailed writeup by Sanjok Karki), and vendor-released patch v2026.4.0 fully addresses the issue via GitHub PR #7372. Self-hosted installations are unaffected due to endpoint access restrictions. CVSS 8.9 reflects high confidentiality, integrity, and availability impact with high attack complexity and high privilege requirements.

RemediationAI

Upgrade Bitwarden Server Cloud to version 2026.4.0 immediately, which implements authorization validation via GitHub PR #7372 (commit 0918bfdda6f). For Bitwarden Cloud customers, the vendor likely applies this patch to their hosted infrastructure automatically, but administrators should verify their instance version through the admin console and confirm upgrade completion with Bitwarden support if uncertainty exists. Self-hosted installations require no action as the vulnerable endpoint is disabled in these deployments. As interim compensating controls while awaiting patch deployment, organizations using provider features should audit all provider-client associations via the admin console to detect unauthorized organization additions, revoke provider service user access for accounts not requiring MSP management capabilities (reducing attack surface), enable comprehensive audit logging for provider API operations to detect exploitation attempts, and implement anomalous API activity monitoring specifically for POST requests to /providers/*/clients/* endpoints. These mitigations reduce but do not eliminate risk since detection is reactive rather than preventive. Full remediation requires upgrading to v2026.4.0. Review GitHub release notes for any deployment considerations: https://github.com/bitwarden/server/releases/tag/v2026.4.0.

Affected VersionsENISA

Server 0 <2026.4.0

Affected Packages

euvd server fix: 2026.4.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability stems from a missing authorization check (CWE-862) in Bitwarden Server's provider management API endpoint. Bitwarden uses a provider-client model where Managed Service Providers (MSPs) manage multiple customer organizations. The vulnerable endpoint POST /providers/{providerId}/clients/existing was designed to add existing organizations to a provider's management scope, but failed to verify whether the authenticated provider service user had legitimate authority over the target organization. This authorization gap is particularly critical in multi-tenant SaaS environments where tenant isolation is paramount. The endpoint includes a SelfHosted(NotSelfHostedOnly = true) attribute, restricting this functionality to Bitwarden's Cloud platform only, which explains why self-hosted deployments are unaffected. The fix in commit 0918bfdda6f implements proper authorization validation before allowing organization-provider association.

Know when Bitwarden gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.9 HIGH
CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (VulnCheck) · only source for this CVE.

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
High
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

Lifecycle Timeline

2
CVSS changed
May 11, 2026 - 18:22 NVD
8.0 (HIGH) 8.9 (HIGH)
CVE Published
May 11, 2026 - 17:14 nvd
HIGH 8.9

DescriptionCVE.org

Bitwarden Server prior to v2026.4.0 contains a missing authorization vulnerability that allows a provider service user to add an arbitrary organization to their provider via POST /providers/{providerId}/clients/existing, resulting in takeover of the target organization; self-hosted installations are unaffected as this endpoint is restricted to Cloud via SelfHosted(NotSelfHostedOnly = true).

Executive ViewAI

Why It Matters

Bitwarden Server Cloud contains a critical authorization flaw allowing authenticated provider users to seize control of any organization without victim consent, enabling complete administrative access to sensitive business data and credentials. Organizations using Bitwarden Cloud as a provider service face immediate risk of organizational takeover and credential compromise by internal or compromised user accounts. Self-hosted deployments are not affected.

Business Impact: Severe
Compensating Controls

Apply vendor patch v2026.4.0. Interim mitigation pending patching: restrict POST /providers/{providerId}/clients/existing endpoint access to trusted networks via firewall/WAF rules and disable or suspend low-privilege provider service accounts until patched.

Threat Intelligence Overview

EPSS Score
0.0%
Top 86% exploitable
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

64
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2026-60104 CRITICAL POC
9.3 Jul 08

Account takeover in self-hosted Bitwarden Server before 2026.6.0 lets a low-privileged organization member steal any oth

CVE-2026-43640 HIGH POC
8.6 May 11

Authentication bypass in Bitwarden Server versions prior to 2026.4.1 allows authenticated users with SCIM management pri

CVE-2026-101878 HIGH POC
7.7 Sep 29

Authentication bypass in self-hosted Bitwarden Server versions 2025.6.0 through 2026.5.0 backed by Microsoft SQL Server

CVE-2023-27974 HIGH POC
7.5 Mar 09

Bitwarden through 2023.2.1 offers password auto-fill when the second-level domain matches, e.g., a password stored for a

CVE-2026-57520 HIGH POC
7.1 Jun 25

Privilege escalation in self-hosted Bitwarden Server before 2026.5.0 lets an authenticated organization member holding a

CVE-2023-27706 HIGH POC
7.1 Jun 09

Bitwarden Windows desktop application versions prior to v2023.4.0 store biometric keys in Windows Credential Manager, ac

CVE-2026-71959 MEDIUM POC
6.9 Aug 10

Audit log integrity across all Bitwarden Server organizations can be undermined by any authenticated user, who may injec

CVE-2026-57521 MEDIUM POC
5.3 Jun 25

Broken access control in Bitwarden Server before 2026.5.0 exposes organization billing data to any authenticated user vi

CVE-2026-43638 MEDIUM POC
5.3 May 11

Bitwarden Server prior to v2026.4.1 allows any authenticated user to write ciphers (encrypted credentials) into arbitrar

CVE-2026-42994 HIGH
8.8 May 01

Malicious code injection in Bitwarden CLI 2026.4.0 distributed via npm for 90 minutes on April 22, 2026, enables remote

CVE-2020-15879 HIGH
7.5 Jul 21

Bitwarden Server 1.35.1 allows SSRF because it does not consider certain IPv6 addresses (ones beginning with fc, fd, fe,

CVE-2019-19766 HIGH
7.5 Dec 12

The Bitwarden server through 1.32.0 has a potentially unwanted KDF. Rated high severity (CVSS 7.5), this vulnerability i

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy