Read 2026-10-04
bitwarden/server: technical due diligence, read from its repository
What Borehole read in bitwarden/server's code and history at aa786fc: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE.txt: Relicensed: GPL-3.0 → AGPL-3.0 (2016-12-03)
Architecture & Codebase — including AI provenance
strongutil/Migrator/DbScripts/2017-08-19_00_InitialSetup.sql is 4,464 lines, 117× this codebase's median file
adequateThe median source file here is 38 lines. 23 files exceed 1,000 lines, the largest being 4,464. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
util/Migrator/DbScripts/2017-08-19_00_InitialSetup.sql:1 — 4,464 lines (117× median) |
util/RustSdk/rust/src/rsa_keys.rs:1 — 3,009 lines (79× median) |
src/Api/Vault/Controllers/CiphersController.cs:1 — 1,937 lines (50× median) |
src/Core/Platform/Mail/HandlebarsMailService.cs:1 — 1,658 lines (43× median) |
util/Migrator/DbScripts/2021-07-22_00_Provider.sql:1 — 1,500 lines (39× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strong10 files still carry code deprecated more than two years ago
adequate10 files were marked deprecated over two years ago and still are, the oldest since Jan 2022. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
src/Core/Utilities/JsonHelpers.cs — deprecated since Jan 2022 |
src/Api/Models/Request/DeviceVerificationRequestModel.cs — deprecated since Feb 2023 |
src/Api/Models/Response/DeviceVerificationResponseModel.cs — deprecated since Feb 2023 |
src/Api/Controllers/DevicesController.cs — deprecated since Mar 2023 |
src/Api/Auth/Models/Request/OrganizationSsoRequestModel.cs — deprecated since May 2023 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v2026.9.2, is not on the branch this survey read; the newest release on it is v2026.8.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2026.9.2 |
Security & Reliability Posture
adequate2 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key. 1 other match set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| 2 cited: Slack token, where fakes are usual |
20 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
bitwarden_license/src/Scim/Dockerfile — runs as root |
bitwarden_license/src/Sso/Dockerfile — runs as root |
src/Admin/Dockerfile — runs as root |
src/Api/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate15 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 1 step pipes a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/_move_edd_db_scripts.yml:54 — action pinned by tag |
.github/workflows/_move_edd_db_scripts.yml:62 — action pinned by tag |
util/SeederApi/Dockerfile:19 — download piped into a shell |
7 locked dependencies have published vulnerabilities, 2 high or critical in what ships
adequate7 of 760 locked dependencies match 9 published advisories in OSV, 5 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
bitwarden_license/src/Commercial.Infrastructure.EntityFramework/Commercial.Infrastructure.EntityFramework.csproj — AutoMapper 14.0.0: GHSA-rvv3-g6hj-g44x (high), fixed in 16.1.1; the project marks it as not affecting it, which is a question to ask |
bitwarden_license/src/Scim/packages.lock.json — Microsoft.OpenApi 2.4.1: GHSA-v5pm-xwqc-g5wc (high), fixed in 2.7.5 |
bitwarden_license/src/Commercial.Infrastructure.EntityFramework/packages.lock.json — SQLitePCLRaw.lib.e_sqlite3 2.1.6: GHSA-2m69-gcr7-jv3q (high) |
Relicensed: GPL-3.0 → AGPL-3.0 (2016-12-03)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
LICENSE.txt — GPL-3.0 from 2016-10-10 |
LICENSE.txt — AGPL-3.0 from 2016-12-03 |
Observability & Operations
strongNo error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on bitwarden/server: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.