- 运维/研发团队共享生产环境凭据:密钥在用户端生成、服务端只存密文,管理员拿到数据库也解不开,这是它和 Bitwarden 自托管、Vault 的核心分野
- 需要审计「谁在什么时候看了哪条密码」的合规场景:访问记录由 API 侧留存,比共享 1Password 账号或 Excel 强得多
- 隔离网络内网部署:不收集遥测、可跑在 Docker/K8s 和树莓派上,适合没有外网出口的环境
- 自动化流水线取凭据:JSON API 可被 CI/脚本调用,但要先想清楚机器身份怎么管,见 pitfalls
passbolt_api
passboltAGPL-3.0活跃维护 有专家点评面向团队的开源密码管理器后端 API,基于 PHP 和 CakePHP 构建,集中存储和共享凭据,解决多人协作时密码分发与权限管控问题。
Passbolt Community Edition (CE) API. The JSON API for the open source password manager for teams!
专家点评
上手难度:进阶更新于 2026-11-11团队共享凭据的端到端加密后端,顶替自建 Vault 或把密码塞进 Confluence 的做法
适用场景
踩坑
- 功能边界比想象中窄:issue 里文件附件、TOTP/2FA 密钥、安全笔记、多密钥类型、标签分类这几类需求反复被提且反应数最高,说明当前版本更接近「纯密码条目」而非通用密钥库。要存 SSH 私钥、证书、TOTP 种子的团队会撞上
- 安装没有一条命令能跑通:README 只给各平台文档链接,实际要按 Docker/K8s/发行版页面逐项配,还要处理 GPG 密钥、TLS、数据库和健康检查,属于「读文档配一遍」起步
- 二次分发有法律约束:AGPL 第 7(e) 条对 Passbolt 名称有商标限制,把它打包进自己产品对外发布前要先看许可,这不是技术问题但会卡住集成方案
同类对比
自托管且要通用密钥类型(SSH、证书、TOTP)选 Vault;要开箱即用的团队密码共享且能接受非纯 E2EE 架构,Bitwarden 自托管或 1Password Teams 分流更省事
README 未给出可直接执行的安装命令,仅链接到 Docker、Kubernetes 及各发行版的安装页面README 未说明具体硬件或显存要求,仅列出可部署于 Docker、Kubernetes 及 Ubuntu、Debian、RedHat、树莓派等系统。
项目说明
由 README 自动翻译提炼面向团队的开源密码管理器 API,集中存储并端到端加密共享凭据
面向团队的开源密码管理器后端 API,基于 PHP 和 CakePHP 构建,集中存储和共享凭据,解决多人协作时密码分发与权限管控问题。
核心能力
- 用户自持密钥,端到端加密存储凭据
- 支持团队内安全共享密码并审计访问
- 提供 JSON API 供客户端与自动化集成
- 可部署在隔离网络环境且不收集遥测
- 提供浏览器扩展、移动端与 CLI 客户端
容易踩的坑
README 未提供本地安装步骤,需按官网对应平台的安装文档操作;安全漏洞不要提 GitHub issue,需走官方披露流程;Passbolt 名称受商标限制,二次分发需注意 AGPL 第 7(e) 条
- v5.17.0Mad World最新正式版2026-10-20 · 2026-10-20 11:57 UTC
Song: https://www.youtube.com/watch?v=Hef-Zf6frk0
Passbolt 5.17.0 "Mad World" introduces passkeys for multi factor authentication, improves autofill reliability across websites, makes permission changes easier to review when moving resources, and brings PIN code resources to QuickAccess. This release also includes security fixes and performance improvements.
Passkeys for MFA
Passbolt 5.17 adds passkeys as a second authentication factor, alongside the TOTP, Yubikey OTP and Duo providers that are already supported. It answers a requirement that many organisations now include in their procurement processes: multi-factor authentication that resists phishing, which one-time codes cannot provide.
Built on the WebAuthn/FIDO2 standard, it is bound to the domain of the Passbolt instance, and the browser refuses to use it anywhere else, so a lookalike site has nothing to capture. Basically, one-time code can be typed into a fake login page and relayed to the real site by an attacker. Passkeys cannot be used this way and protects against this kind of phishing.
Passkeys are available in every edition. Once an administrator enables them in Administration > Multi-factor authentication, each user can register up to ten passkeys from Profile > Multi-factor authentication, using a security key such as a YubiKey or the biometrics built into their laptop, phone, such as Touch ID or Windows Hello.
From then on, Passbolt asks for the passkey right after sign-in, as it does for the other providers. Users can tick "Remember this device for a month" to skip the check on a trusted device, or leave it unticked to verify every time. Organisations using Passbolt Pro edition, and wanting a stricter posture can disable this option in the Multi-factor authentication policy settings, so that every sign-in requires the passkey.
This first step covers multi-factor authentication. Storing passkeys for third-party websites as a resource type and Passwordless sign-in to Passbolt will follow in upcoming releases.
A new autofill detection engine
Autofill is a core part of the Passbolt browser experience, and version 5.17 rebuilds its detection engine from scratch. It tackles two familiar frustrations: no autofill on a form that clearly needs it, and an autofill icon in a field that has nothing to do with credentials.
Getting this right is harder than it looks, because no two websites build their forms the same way. Field names differ, labels come in many languages, and the underlying code varies widely from one site to the next. A handful of regular expressions could only go so far, and the previous engine had reached its limits.
The new engine understands the context of each field, from the structure of the form to the labels around it, before deciding whether to step in. The first benchmarks are very promising: on our internal test set, form detection rises from 74% with the previous engine to 93.4%, while processing cost stays low.
A test set is not the web, though, and this is where the community comes in: we are eager to hear how the engine behaves on the websites our users rely on every day. For those curious about the inner workings, a detailed blog post will follow.
Safer permission handling during resource moves
Passbolt 5.17 brings the permission review introduced in 5.14 to moves of resources and folders. Creating a resource in a shared folder, editing a shared resource and now moving items all ask for the same explicit confirmation.
A move needs this step because placing a resource in a shared folder, or taking it out of one, can change who has access to it. Previously, users chose between keeping the current permissions and applying those of the destination folder, without seeing what either opti
- v5.16.0Enjoy the Silence2026-09-17 · 2026-09-17 10:01 UTC
查看更新说明
Song: https://www.youtube.com/watch?v=gI6fQ2IXMjE
Passbolt 5.16.0 introduces Offline Mode, allowing users to access their credentials when the Passbolt server is unreachable.
Offline mode (Beta)
During server maintenance, data center interventions, or network outages, teams lose access to critical credentials needed to restore systems, if those credentials are locked inside an unreachable Passbolt server.
Offline mode closes this availability gap by providing secure read-only access to essential credentials when the server is unreachable. This ensures business continuity, satisfies compliance mandates for disaster recovery, and eliminates the need for insecure, stale manual exports.
The administrator enables Offline Mode in the administration settings and can use Role-Based Access Control (RBAC) to refine which roles have access.
Individual users allowed to access the capability can then select and mark specific resources within the application to make them available offline. Once marked for offline use, credentials can be accessed directly via the QuickAccess menu in the Passbolt browser toolbar.
Offline storage is limited to a maximum of 1,000 resources per user. The feature currently supports only password and TOTP resource types with encrypted metadata. Upcoming releases will add support for other resource types and the ability to mark resources offline in bulk.
Security Considerations
Offline resources are accessible for 5 minutes per session by default and encrypted information persists in browser storage for up to 7 days without server connectivity. Passbolt Pro allows administrators to adjust both session durations and data retention limits to align with organisational compliance requirements.
Once synchronised, credentials marked for offline access are cached on every browser connected to the same Passbolt account making them available across all devices.
Beta Testing
Because Offline Mode is in Beta and will be undergoing a third-party security review, it should be used for testing purposes only. A follow-up blog post covering its mechanics, limitations, and additional security considerations will be published soon.
We welcome your feedback if you test it on a non-production instance.
Maintenance and security
As usual, this release ships a round of third-party dependency upgrades and security advisory fixes, with no user-visible impact. It also addresses minor bugs reported by the community. Check out the changelog for more information.
Conclusion
Many thanks to everyone who provided feedback, reported bugs, and contributed to making Passbolt better!
Changelog
Added
- PB-52633 Add support for Offline Mode
Fixed
- PB-54100 Fix account recovery notifications are sent to deleted admins
- PB-54504 Fix MissingTemplateException on .json endpoints when X-Requested-With: XMLHttpRequest is set
- PB-54574 Fix lock-wait-timeout on DELETE during group edit that removes a user
Security
- PB-54489 Upgrade phpseclib/phpseclib to 3.0.57 (CVE-2026-84308, AIKIDO-2026-730961)
- PB-54532 Small upgrade for js-yaml
Maintenance
- PB-49136 Update cakephp/migrations package to improve compatibility with PHP 8.5
- PB-53658 Use Request to DTO Mapping to automatic mapping of request data
- PB-53925 Add tests to assert session data do not trigger any code
- PB-54144 Update the Passbolt logo
- Renovate: Update adminer:standalone Docker digest
- Renovate: Update dependency cakephp/cakephp to v5.4.2
- Renovate: Update dependency composer/composer to v2.10.3
- Renovate: Update dependency league/flysystem to v3.35.3
- v5.15.0Who Is He2026-08-21 · 2026-08-21 08:11 UTC
查看更新说明
Song: https://youtu.be/SLNqxQXMV1w?si=M3l6Zz4GffohF-OZ
Passbolt 5.15.0 improves form detection for autofill, makes permission changes easier to review, and adds several security and administration improvements. This release also introduces new session management tooling and additional safeguards for Passbolt Pro.
Clearer permission confirmation changes
Permission changes are now easier to understand before they take effect, helping users avoid accidental access changes. New badges clearly show whether a permission is being added, modified, or deleted, so users can see exactly what will change at a glance.
Deleted permissions can also be rolled back to their original state before confirmation, making access changes easier to review and adjust.
Improved autofill detection
Autofill now works more reliably on modern websites that were previously unsupported. Improved form detection helps users fill credentials more consistently and with less manual effort, resulting in a smoother autofill experience.
This is the first step in a broader series of autofill improvements, with upcoming releases focused on reducing false positives and further refining form classification. A technical blog article explaining those improvements in detail will be published after the next release.
Security
Invalidate JSON authentication token for disabled users
Disabling a user now cuts off their access straight away when they are signed in with JWT authentication, as was already the case for other authentication methods. Previously, a user who had just been disabled could keep using the API for up to 5 minutes. Only the mobile application and power users with a custom API integration were affected.
Last login dates only available for administrators
Privacy has also been strengthened by restricting users' last login dates to administrators only, reducing unnecessary exposure of sensitive account activity.
SCIM administrators protected against deletion (Pro Edition)
SCIM providers can no longer delete Passbolt administrators by default, helping prevent an identity provider from accidentally locking an administrator out.
Organisations that intentionally manage administrator removal through SCIM can disable this protection by updating their configuration.
If you installed Passbolt with packages, open
/etc/passbolt/passbolt.phpand add or update the plugins section:[...] // plugins configuration. 'plugins' => [ 'scim' => [ 'security' => [ 'allowDeleteAdministrators' => true ] ], ], [...]If you installed Passbolt with docker, you can use the following environment variable:
PASSBOLT_PLUGINS_SCIM_SECURITY_ALLOW_DELETE_ADMINISTRATORS=trueSSRF protection for SSO provider URLs (Pro Edition)
SSO provider integration is now blocked from accessing internal or private network addresses, reducing the risk of malicious or misconfigured redirects. A new healthcheck flags when the protection is disabled. It remains off by default for backward compatibility and will become the default in a future release.
Organizations that would want to enforce it could already do it by configuration.
If you installed Passbolt with packages, open
/etc/passbolt/passbolt.phpand add or update the plugins section:[...] 'security' => [ 'sso' => [ 'egress' => [ // Master switch for the SSRF guard 'enabled' => true, // Enforce vs. warn-only // true blocks the connection // false logs a warning but still connects 'block' => true, // Turn the always-blocked category on/off (link-local + cloud metadata) 'blockLinkLocal' => true, // Turn the private-range category on/off (loopback, RFC1918, unique local addresses, carrier-grade NAT) 'blockPrivateRanges' => true, - v5.14.3Going Backwards2026-08-06 · 2026-08-06 13:37 UTC
查看更新说明
Song: https://youtu.be/pIqrmGKfmQU
Passbolt 5.14.3 addresses issues identified after the 5.14 release.
Following the introduction of the permission confirmation dialog in 5.14, two behaviors needed correction. The dialog appeared when editing only the metadata of a shared resource, such as renaming it, even though no secret was changed. It now appears only when the secret is modified. Additionally, when creating a resource in a shared folder where the user is not the owner, the dialog allowed editing the permissions inherited from the parent folder, potentially overriding the access structure established by the organization. The dialog now opens in read-only mode in this situation, allowing the user to review permissions and group members before proceeding without overriding the permissions. Users authorized to manage access can still update permissions directly.
Additionally, the in-form menu could appear even when disabled on the API by feature flag. The API could in some cases return plugin configuration in an unexpected format, and the browser extension would fall back to enabling any plugin whose setting did not strictly match. Both the API and the browser extension now enforce a strict format, and the in-form menu correctly reflects the settings.
Finally, a separate regression prevented the API from running over HTTP. While this is not recommended, the regression could break testing or staging instances not using HTTPS.
Many thanks to everyone who reported these issues.
Changelogs
Fixed
- PB-53457 Fix env()-backed config flags to enforce strict boolean type
- PB-53498 Fix CSRF cookie not working over HTTP deployments
- v5.14.0Sunshine2026-07-28 · 2026-07-28 13:32 UTC
查看更新说明
Song: https://youtu.be/JfP3sB-hke4
Passbolt 5.14.0 Sunshine introduces explicit permission confirmation prompts to improve control over shared resources. This release also addresses a security issue related to MFA policy enforcement and includes usability improvements.
Sharing transparency
Users now receive an explicit confirmation dialog before creating items in shared folders or editing shared resources. This provides full permission transparency before changes take effect, preventing accidental privilege exposure.
In addition, when a group appeared in the access list, its individual members were not visible, making it difficult to assess the actual reach of shared access. Group members are now displayed directly within the dialog.
As the first stage of a broader security initiative, future updates will extend these confirmations to folder move operations and offer enhanced permission preview dialogs.
Edition and Subscription Management
The Passbolt edition is now visible in the application footer, and Terms & Credits links have moved to the main navigation menu.
Additionally, whenever administrators downgrade to the Community edition they will be explained the impact on data and feature beforehand so they can make an informed decision.
Resource Suggestions
Suggested resources in the browser extension are now ranked using an improved URL relevance algorithm. Exact URL matches appear first, followed by parent paths and domain matches, allowing users to select the correct credentials faster and with fewer autofill errors.
Security Improvements
This release addresses a low-severity vulnerability that allowed a user with a valid account and MFA access to remember their device for a month even when the organisation had disabled that option. Reported by security researcher Damir, the issue affected Passbolt API versions up to 5.13.0 and is now enforced correctly at the API level in 5.14.0.
Additional Improvements
Passbolt Pro extends email-free account setup and recovery to OIDC and ADFS SSO providers, improving onboarding by integrating directly with enterprise identity management systems.
Finally, this release lays the foundational backend architecture required for upcoming offline functionality.
Conclusion
Many thanks to Damir and everyone who provided feedback, reported bugs, and contributed to making Passbolt better!
Changelogs
Added
- PB-49943 Add a model cache health check service
- PB-50621 Add recover flow support for OAuth2 & ADFS SSO providers
- PB-52153 Add a command to insert dummy data into the email_queue table
- PB-52421 Add more verbose logs when an SSO provider response is in an incorrect format
Fixed
- PB-48004 Fix deprecation warnings in makeCsrfCookieSecureIfRequestIsSsl
- PB-52585 Fix resource sharing after inserting dummy data
- PB-52727 Fix typo in SSO settings activated email
- PB-52952 Return 400 instead of 409 when the email is not found in the expected place from a SCIM IdP
- PB-52592 Fix account recovery response email not being sent to custom RBAC roles
Security
- PB-29515 Fix MFA remember me policy bypass (INC-2046)
- PB-32421 Validate and filter user-edit request data via a modeless form instead of
UsersEditController::_validateRequestData - PB-51819 Upgrade composer/composer (AIKIDO-2026-688935)
- PB-52440 Fix a disabled TOTP provider still being able to mint an MFA verification cookie via non-JSON
/mfa/verify/totp - PB-52441 Fix refresh-token rotation being replayable concurrently due to non-atomic consumption
- PB-52452 Harden secret revocation on share
- PB-52457 Block renaming of reserved roles to close a delete-protection bypass
- PB-52461 Fix last-resource-type guard incorrectly counting soft-deleted rows
- PB-52463 Restrict
filter[is-deleted]on the resource-types index to admins only - PB-52538 Upgrade js-yaml
- PB-52599 Upgrade spomky-labs/otphp (GHSA-g7m4-839x-ch6v, GHSA-2jx3-
用户点评
登录用户的真实使用记录,可按版本和硬件筛选还没有人点评。第一个说出真实体验的人最有价值。
The open source password manager for teams.
- Introducing Passbolt
- Get Started
- Available Clients & Apps
- Contributing
- Reporting a security issue
- License

Introducing Passbolt
Passbolt is a security-first, open source password manager for teams. It helps organizations centralize, organize and share passwords and secrets securely.
What makes passbolt different?
- Security: Passbolt security model features user-owned secret keys and end-to-end encryption. It is audited multiple times annually, and findings are made public.
- Collaboration: Securely share and audit credentials, with powerful and dependable policies for power users.
- Privacy: Passbolt is headquartered in the EU :european_union: specifically in Luxembourg. Passbolt doesn't collect personal data or telemetry, and can be deployed in an air-gapped environment.
Get Started
Run it on your own server, natively
Available Clients And Apps
Browser Extensions
Mobile Apps
CLI
Install passbolt CLI tool: go-passbolt-CLI
Desktop App
Coming soon see the pre-alpha version here.
Contributing
Please check CONTRIBUTING.md for more information about how to get involved.
Reporting a security Issue
If you've found a security related issue in Passbolt, please don't open an issue on GitHub. Follow our responsible disclosure process: https://www.passbolt.com/docs/contribute/security/vulnerability/.
License
This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License (AGPL) as published by the Free Software Foundation version 3.
The name "Passbolt" is a registered trademark of Passbolt SA, and Passbolt SA hereby declines to grant a trademark license to "Passbolt" pursuant to the GNU Affero General Public License version 3 Section 7(e), without a separate agreement with Passbolt SA.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License along with this program. If not, see GNU Affero General Public License v3.