Vaultwarden
Vaultwarden: Brute-force protection bypass vulnerability
Vaultwarden is a Bitwarden-compatible server written in Rust. Prior to 1.35.4, there is a security vulnerability in Vaultwarden that allows bypassing the login brute-force protection if email 2fa is enabled. If email 2fa is enabled, the unprotected 2fa-function send_email_login (email.rs, api endpoint /api/two-factor/send-email-login) also acts as an oracle determining whether a username-password combination is correct. An attacker can abuse that endpoint to brute-force passwords without rate-limiting. This works even for users who don't have email 2fa configured. This vulnerability is fixed in 1.35.4.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.35.4
Fixed in 1.35.4
Mitigation
Upgrade vaultwarden to 1.35.4 or later.
References
- Vendor advisory github.com/dani-garcia/vaultwarden/security/ad…
- Patch github.com/dani-garcia/vaultwarden/pull/6867
- Release notes github.com/dani-garcia/vaultwarden/releases/ta…
Timeline
Days relative to CVE publicationFirst public PoC 105 days after publication; not in CISA KEV. First PoC: Boreas37/CVE-2026-43914-PoC (created 24 Aug 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Boreas37/CVE-2026-43914-PoC | 24 Aug 2026 +105 d | 1 | PoC
Flags · score 25
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.