Skip to main content
Menu
CVEs

LessPass brute force possible on JWT login endpoints

Affects the LessPass self-hosted sync server backend before commit 9469b0c, which lacks rate limiting on JWT login. CVSS rates it critical at 9.1. Fixed in commit 9469b0c.

CVE-2026-133872Published , updated

9.1CriticalCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

LessPass, a self-hosted sync server backend before commit 9469b0c, lacks rate limiting on its JWT login endpoints, so there is no limit on authentication attempts. An attacker on the network, without logging in, can brute force passwords or use credential stuffing against known account emails to obtain tokens that grant read and write access to stored profiles.

Written by a model

Original description

LessPass self-hosted sync server backend before commit 9469b0c lacks rate limiting on the JWT login endpoints /tokens/auth/ and /auth/jwt/create/, allowing unlimited authentication attempts. Unauthenticated remote attackers can brute force passwords or perform credential stuffing against known account emails to obtain tokens granting read and write access to stored profiles.

Who should check

Anyone running the LessPass self-hosted sync server backend before commit 9469b0c, including teams hosting their own LessPass sync server

“LessPass self-hosted sync server backend before commit 9469b0c”

vulncheck.com

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133872 (LessPass Backend before Commit 9469b0c Missing Rate Limiting on JWT Login), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133872 (entry last updated 2026-11-20):
Affected:
- lesspass lesspass: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affected LessPass self-hosted sync server backend before commit 9469b0c (source: https://www.vulncheck.com/advisories/lesspass-backend-before-commit-9469b0c-missing-rate-limiting-on-jwt-login)
- Affected versions are master HEAD as of 2026-10-30 before the fix commit (source: https://github.com/lesspass/lesspass/security/advisories/GHSA-4mwq-gh5h-pxjg)
- No DEFAULT_THROTTLE_CLASSES is configured in the Django REST Framework settings and no view sets throttle_classes (source: https://github.com/lesspass/lesspass/security/advisories/GHSA-4mwq-gh5h-pxjg)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-133872 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133872 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/lesspass/lesspass/security/advisories/GHSA-4mwq-gh5h-pxjg
- https://github.com/lesspass/lesspass/commit/9469b0cb90b5a79e2ab4f7f07bb67318dd312b99
- https://github.com/lesspass/lesspass
- https://github.com/lesspass/lesspass/blob/d8f29da390d4492a5ea7c106779c93f71aa976ff/backend/lesspass/settings.py
- https://www.vulncheck.com/advisories/lesspass-backend-before-commit-9469b0c-missing-rate-limiting-on-jwt-login
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133872
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133872"}.

Affected versions

cve.now Index

26Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.1/10CVSS 9.1
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Evidence 7

Questions about CVE-2026-133872

Is CVE-2026-133872 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The JWT login endpoint of the LessPass sync server backend has no rate limiting, so repeated login attempts against known account emails are not throttled. Successful logins return tokens with read and write access to stored profiles.

Source: vulncheck.com, github.com

Am I affected, and how do I check?

The advisory lists master HEAD as of 2026-10-30 before the fix commit as affected. The backend defines no DEFAULT_THROTTLE_CLASSES in its Django REST Framework settings and no view sets throttle_classes. To check a copy, compare its commit history against commit 9469b0c and search the settings for DEFAULT_THROTTLE_CLASSES.

Source: vulncheck.com, github.com

How do I fix CVE-2026-133872?

Update the LessPass backend to commit 9469b0c or later. The sources give no release version for the fix.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.