External risk intelligence

LessPass Self-Hosted Sync Server JWT Login Rate Limiting Bypass

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-133872

The vulnerability exists in a self-hosted sync server backend, specifically on JWT login endpoints. These components are typically deployed as internet-facing services or APIs to allow users to sync data remotely across devices, making them commonly exposed to the public internet in standard deployment patterns.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in the LessPass self-hosted sync server backend that could allow unauthenticated attackers to attempt unlimited logins. If exploited, this could enable unauthorized access to stored user profiles, potentially exposing sensitive information. The primary concern is to confirm if this technology is in use and assess any exposure.

  • Unlimited login attempts allow unauthorized access.
  • Protects stored profiles from unauthorized viewing.
  • Confirm LessPass sync server use and exposure.

Attack Path

How an attacker could exploit the issue

Attackers can reach the LessPass self-hosted sync server by leveraging its network exposure. Without rate limiting on JWT login endpoints, an unauthenticated remote attacker can repeatedly attempt to guess credentials. Successfully compromising an account allows the attacker to gain read and write access to stored profiles.

  • No authentication required for access.
  • Brute-forcing JWT login endpoints.
  • Unauthorized access to stored profiles.

Live Threat

Current exploitation, exposure, and threat context

A self-hosted LessPass sync server could expose stored user profiles when rate limiting is not applied to its JWT login endpoints. This could allow unauthenticated attackers to attempt numerous logins to gain unauthorized read and write access to profiles.

  • Stored user profiles.
  • Brute force or credential stuffing attacks.
  • Unauthorized access to profile data.

Operational Fix

Recommended remediation, mitigation, and detection steps

The LessPass self-hosted sync server's lack of rate limiting on JWT login endpoints makes it susceptible to brute-force attacks, potentially exposing stored user profiles. The team responsible for the LessPass backend, likely an internal development or infrastructure team, must first identify all instances of the self-hosted sync server. Confirming external reachability and business criticality will help prioritize remediation efforts, which may involve vendor coordination or an upgrade once the issue is addressed in the codebase.

  • Identify LessPass self-hosted sync server instances.
  • Verify external reachability and business criticality.
  • Plan upgrade or risk mitigation strategy.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the LessPass self-hosted sync server?

LessPass is an open-source password manager designed to generate passwords algorithmically without needing to store them in a database. The self-hosted sync server is an optional backend component that allows users to store and synchronize their encrypted profile data across multiple devices. Organizations or individuals deploy this server to maintain control over their data infrastructure rather than relying on a centralized cloud service.

What is the weakness in CVE-2026-133872?

This vulnerability is classified as CWE-307: Improper Restriction of Excessive Authentication Attempts. In plain terms, the server fails to limit how many times someone can try to log in within a specific timeframe. Because the JWT login endpoints lack this "rate limiting," an attacker can automate thousands of password guesses or perform credential stuffing attacks against the system without being blocked by the server.

How does an attacker trigger this vulnerability?

An unauthenticated remote attacker triggers this by sending repeated requests to the /tokens/auth/ or /auth/jwt/create/ endpoints. This bug relies specifically on the absence of login request throttling. It is important to note that this is not a flaw in the password generation logic itself, nor does it require the attacker to have any existing session or account permissions to begin their brute-force attempts.

Is my LessPass server at risk?

According to Halo Surface Signal, because this component is intended to sync data across devices, these servers are frequently deployed as internet-facing services. If your LessPass sync instance is reachable from the public internet, it is effectively exposed to these automated login attempts. Internal-only instances that are not exposed to the public network are at a significantly lower risk of being targeted by external actors.

How do I secure my LessPass environment?

Begin by identifying all running instances of the self-hosted LessPass sync server within your infrastructure. Once identified, verify whether these servers are accessible from the internet. If they are, prioritize restricting access to these endpoints until the underlying software can be updated to a version that includes rate limiting. Consult the project's official repository for details on the specific commit or release that addresses this authentication flaw.

References