/

CVE-2026-43639

Severity:

HIGH RISK

(8.0)

Missing Authorization in Bitwarden Cloud Provider

CVE-2026-43639

Analyzed

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Account and Organization Takeover

Severity:

HIGH RISK

(8.0)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A missing authorization check in Bitwarden Server's cloud-only provider API allows a provider service user to attach any arbitrary organization to their provider account via the POST /providers/{providerId}/clients/existing endpoint.

Under certain conditions in Bitwarden Cloud, this can result in takeover of the target organization, while self-hosted installations are not affected because this endpoint is restricted to cloud use only.

Affected context

This vulnerability occurs in Bitwarden Server deployments running in Bitwarden Cloud, specifically within the provider service functionality.

It affects scenarios where:

  • Providers can manage or onboard organizations through the POST /providers/{providerId}/clients/existing API endpoint.
  • The system does not verify that the requesting provider is authorized to manage the target organization being added.
  • The environment is flagged as Cloud (SelfHosted(NotSelfHostedOnly = true)), meaning self-hosted instances do not expose this behavior.

Exploit preconditions

  • Attack surface: Bitwarden Cloud API endpoint POST /providers/{providerId}/clients/existing.
  • Required access: Valid provider service user account or credentials that can call the provider API in the cloud environment.
  • Trigger point: Submission of a crafted request to add an existing organization as a client to the attacker-controlled provider, without proper authorization checks on the organization relationship.
  • Why exploitation is possible: The server performs authentication of the provider user but fails to enforce an authorization constraint that ensures the provider has legitimate rights to link the specified organization, enabling unauthorized association and control.

Why this happens

The core issue is a missing authorization step when processing requests to associate existing organizations with a provider via POST /providers/{providerId}/clients/existing.

While the user making the request is authenticated as a provider service user, the system does not sufficiently validate that they are permitted to manage the target organization identifier included in the request.

This maps to CWE-862: Missing Authorization, where the application relies on authentication alone and omits a critical authorization decision, allowing operations to be performed on resources outside the caller's permitted scope.

Potential impact

  • Unauthorized takeover of an existing Bitwarden organization by linking it to an attacker-controlled provider.
  • Access to organization-level management capabilities, including user, group, or policy administration, depending on provider features.
  • Potential exposure or manipulation of secrets managed under the compromised organization, subject to Bitwarden's sharing and access controls.
  • Abuse of provider workflows to perform unauthorized administrative operations across multiple organizations if systematically exploited.

General mitigation guidance

Effective mitigation focuses on enforcing strict, resource-level authorization for provider-to-organization relationships and minimizing trust assumptions in cross-tenant operations.

Common patterns include:

  • Implementing explicit authorization checks that confirm a provider's right to manage a given organization before creating or updating any linkage.
  • Using a clear ownership and tenancy model where every cross-entity association is validated against a server-side mapping, not client-supplied identifiers alone.
  • Restricting powerful provider APIs to the minimum necessary roles and capabilities, adhering to least privilege for service and administrator accounts.
  • Applying defense-in-depth controls, such as secondary confirmation flows or invitations from the target organization side, for sensitive relationship changes (e.g., organization onboarding to a provider).
  • Designing APIs so that link establishment requires proof of control from both sides of the relationship (provider and organization) rather than unilateral actions.

How teams detect issues like this

Detection generally relies on a combination of application-layer auditability and security review of authorization logic:

  • Code-level review: Examine provider-related handlers for POST /providers/{providerId}/clients/existing and similar endpoints to ensure they invoke centralized authorization checks tied to the target organization resource, not just authentication.
  • Static analysis: Configure rules to flag controller or service methods that perform create/update/delete operations on tenant or organization relationships without passing through a standardized authorization component.
  • Log analysis: Monitor audit logs for anomalous patterns such as providers suddenly gaining access to unrelated organizations, or large spikes in organization-link operations from a single provider account.
  • Security testing: Incorporate multi-tenant authorization test cases in QA and penetration tests, attempting to link or manage organizations that should be outside the tester's permitted scope.

Sources

SourceLink
github.comgithub.com/bitwarden/server/commit/0918bfdda6f5eec391c69bd9074f6aef4eac0b1d
github.comgithub.com/bitwarden/server/pull/7372
github.comgithub.com/bitwarden/server/releases/tag/v2026.4.0
sanjokkarki.com.npsanjokkarki.com.np/blog/bitwarden-provider-takeover
vulncheck.comvulncheck.com/advisories/bitwarden-server-missing-authorization-via-provider-clients

Frequently asked

questions

Yes, but only by authenticated provider service users in Bitwarden Cloud. An attacker must be able to issue requests to the cloud API with valid provider-level credentials; anonymous users cannot exploit this issue directly.

The attacker needs access to a provider account or service user that can call the POST /providers/{providerId}/clients/existing endpoint in the cloud environment. With that access, they can attempt to attach arbitrary organizations as clients to their provider.

The most robust fix is to enforce strict authorization checks on every operation that binds or manages organizations, ensuring that the calling principal is explicitly allowed to control the target organization. This usually means centralizing authorization logic, validating both the acting entity (provider) and the target resource (organization), and rejecting any request where the relationship cannot be proven server-side.

Prevention relies on designing multi-tenant and provider features with explicit, resource-scoped authorization from the outset. This includes:

  • Adopting a consistent access control model with enforced checks on all cross-tenant and administrative operations.
  • Treating client-supplied identifiers for tenants or organizations as untrusted and verifying them against server-managed ownership mappings.
  • Integrating automated authorization tests, code review checklists, and policy-based access controls into the development lifecycle, particularly for new administrative or provider APIs.
Find out what's already
exploitable in your codebase.