listmonk 2FA bypass via brute-forced TOTP codes
Affects listmonk 6.0.0 up to but not including 7.0.0-beta.2, for accounts with two-factor (TOTP) authentication enabled, including Super Admin. Fixed in 7.0.0-beta.2.
- Exploited
- No known exploitation
- Fix
- Fixed in 7.0.0-beta.2
- Who is exposed
- Not reported
Summary
Written by a model
Listmonk 6.0.0 before 7.0.0-beta.2 contains a 2FA bypass vulnerability that allows attackers with a valid password to brute-force TOTP codes because the attempt counter resets on every new password login. Attackers can repeatedly submit credentials to POST /admin/login to obtain fresh tokens, each allowing 15 more guesses, gaining sessions for 2FA-protected accounts including Super Admin.
Who should check
Teams running listmonk 6.0.0 up to 7.0.0-beta.2 with two-factor authentication enabled on admin accounts, including Super Admin accounts
“Listmonk 6.0.0 before 7.0.0-beta.2 contains a 2FA bypass vulnerability”
What to do
Upgrade to a fixed version: 7.0.0-beta.2.
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-128332 (listmonk 6.0.0 before 7.0.0-beta.2 TOTP Brute-Force via /admin/login/twofa), 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-128332 (entry last updated 2026-11-13):
Affected:
- Go package github.com/knadh/listmonk: from 6.0.0, fixed in 7.0.0-beta.2
Fixed versions: 7.0.0-beta.2.
Conditions (all must be true for the bug to be hit):
- Running listmonk 6.0.0 up to but not including 7.0.0-beta.2 (source: https://www.vulncheck.com/advisories/listmonk-6.0.0-before-7.0.0-beta.2-totp-brute-force-via-admin-login-twofa)
- Target account has two-factor (TOTP) authentication enabled (source: https://www.vulncheck.com/advisories/listmonk-6.0.0-before-7.0.0-beta.2-totp-brute-force-via-admin-login-twofa)
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-128332 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128332 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/knadh/listmonk/commit/3f62a55c13dbc679b29238e890e4b90d6d4996d8
- https://github.com/knadh/listmonk/releases/tag/v7.0.0-beta.2
- https://github.com/knadh/listmonk/blob/v7.0.0-beta.1/internal/tmptokens/tmptokens.go#L13-L88
- https://github.com/knadh/listmonk/blob/v7.0.0-beta.1/cmd/auth.go#L514-L568
- https://www.vulncheck.com/advisories/listmonk-6.0.0-before-7.0.0-beta.2-totp-brute-force-via-admin-login-twofa
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-128332
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-128332"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects Go packages
- Severity10/10CVSS 9.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Public exploit activity
- EPSS: 0.43%
- Posted on X by cve.now Nov 13
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-128332 |
| Record | NVD · CVE-2026-128332 |
| Other links 5 | |
| Patch | GitHub · knadh/listmonk · Commit 3f62a55c |
| Repository | GitHub · knadh/listmonk · Release v7.0.0-beta.2 |
| Repository | GitHub · knadh/listmonk · internal/tmptokens/tmptokens.go · L13-L88 |
| Repository | GitHub · knadh/listmonk · cmd/auth.go · L514-L568 |
| Link | vulncheck.com · advisories/listmonk-6.0.0-before-7.0.0-beta.2-totp-brute-force-via-admin-login-twofa |
Questions about CVE-2026-128332
Is CVE-2026-128332 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 login page for two-factor authentication at /admin/login/twofa can be attacked by guessing TOTP codes repeatedly. A successful guess gives the attacker a session for the protected account, which can include Super Admin.
Source: vulncheck.com
Which versions are affected by CVE-2026-128332?
github.com/knadh/listmonk (Go): from 6.0.0 before 7.0.0-beta.2.
Source: cve.now feed data
Am I affected, and how do I check?
Listmonk 6.0.0 up to but not including 7.0.0-beta.2 is affected. The setup that matters is an account with two-factor (TOTP) authentication enabled; check your version in the listmonk admin or your deployed build, and check the account's 2FA settings in the admin user profile.
Source: vulncheck.com
How do I fix CVE-2026-128332?
Upgrade listmonk to 7.0.0-beta.2 or later. The facts name no other patch or workaround.
Source: vulncheck.com
Related
- CVE-2026-128333listmonk 6.0.0 before 7.0.0-beta.2 2FA Bypass via Password Reset Flow
- CVE-2025-49136listmonk's Sprig template Injection vulnerability leads to reading of Environment Variable for low privilege user
- CVE-2025-58430listmonk Vulnerable to CSRF to XSS Chain That Can Lead to Admin Account Takeover
- CVE-2026-34828listmonk: Active sessions remain valid after password reset and password change
- CVE-2026-128334listmonk 6.2.0 before 7.0.0-beta.2 Missing Authentication via Azure Bounce Webhook
- CVE-2026-62361listmonk: SQL Injection in `/api/subscribers/export` bypasses table access control, leaking admin password hashes and SMTP credentials
No corrections so far. Something wrong on this page? Report an error.