CVE-2026-133872: LessPass Login Has No Rate Limit

A critical flaw in the LessPass password manager's self-hosted sync server lets attackers try unlimited passwords against user accounts, because its login pages have no rate limiting. The vulnerability, tracked as CVE-2026-133872 and scored 9.1 out of 10 under CVSS 4.0, was published on 20 November 2026.
LessPass is an open-source password manager that generates passwords algorithmically instead of storing them in a database. Its optional sync server lets users store and synchronise their encrypted profile data across devices. The flaw is in that server's backend: the JWT login endpoints at /tokens/auth/ and /auth/jwt/create/ do not limit how many login attempts can be made, so an unauthenticated remote attacker can send repeated requests without being slowed down or locked out.
The weakness is classified as CWE-307, improper restriction of excessive authentication attempts. In plain terms, the server never says enough. An attacker can automate thousands of password guesses, or run credential stuffing, trying email addresses and passwords leaked from other breaches against LessPass accounts. If a guess succeeds, the server hands over a token granting read and write access to the stored profiles.
How the flaw works
The attack needs no account, no special access and no action from the victim. The login endpoints are reachable over the network by anyone who can reach the sync server, and each attempt is cheap. Because there is no throttle, an attacker can work through large lists of credentials at full speed, and can keep trying for as long as they like.
The flaw does not affect how LessPass generates passwords, and it does not let an attacker read profiles without first guessing or reusing valid credentials. But once valid credentials are found, the consequences are serious: the token returned by the login endpoint gives access to the account's stored profiles, which are the gateway to the passwords the user relies on.
The vulnerability affects LessPass self-hosted sync server backends before commit 9469b0c. The issue was disclosed through a GitHub security advisory, GHSA-4mwq-gh5h-pxjg, and the fix is included in that commit. No fixed release version is listed in the vulnerability data, so administrators should update to the commit or to a later release that contains it.
Why a password manager flaw matters
A password manager is the one service that guards all the others, so a flaw in its login handling carries outsized risk. Credential stuffing works because people reuse passwords: a password exposed in one breach is often valid somewhere else. A login page without rate limiting removes the main obstacle to testing those reused credentials at scale.
Self-hosted sync servers are also easy to overlook. They are typically run by individuals or small teams who installed the server once and left it running, and they may not follow security advisories as closely as a large vendor's customers. Any instance reachable from the internet has been exposed to unlimited login attempts since the flaw was introduced.
The flaw is not listed in CISA's Known Exploited Vulnerabilities catalogue, and there is no public evidence that it has been exploited. But the fix is small and the exposure is easy to check, so there is little reason to delay.
What to do now
Anyone running a LessPass self-hosted sync server should update to commit 9469b0c or a later release containing the fix. Until the update is applied, the login endpoints should not be exposed to the internet: restrict access to trusted networks, or put rate limiting in front of them with a reverse proxy or gateway.
Users of a self-hosted server should also change their LessPass master password if there is any doubt about whether their account was targeted, and check that no unfamiliar devices or sessions have accessed their profiles. Strong, unique master passwords remain the best defence against brute-force and credential stuffing attacks, even when rate limiting is in place.