CVE
listmonk 2FA bypass via brute-forced TOTP codes
Only affects listmonk 6.0.0 up to 7.0.0-beta.2 for accounts with two-factor (TOTP) login enabled. Rated critical by CVSS (9.1). Fixed in 7.0.0-beta.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 7.0.0-beta.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 7.0.0-beta.2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.43% · 37th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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 through 7.0.0-beta.1 with two-factor (TOTP) admin login enabled, including Super Admin accounts.
“Listmonk 6.0.0 before 7.0.0-beta.2 contains a 2FA bypass vulnerability”
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
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
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:
- 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):
- Affects 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)
- The target account has two-factor (TOTP) login 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:
- 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/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"}.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
Affected versions
- knadh listmonk
From 6.0.0 · fixed in 7.0.0-beta.2
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Patch
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
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 two-factor check at /admin/login/twofa can be attacked by guessing TOTP codes repeatedly. A successful guess gives a session for a two-factor-protected account, including Super Admin.Source: vulncheck.com
Which versions are affected by CVE-2026-128332?
listmonk: 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, and only for accounts that have two-factor (TOTP) login enabled. To check, look at the version listmonk reports in its admin interface or installed package, and check whether two-factor login is enabled for the account.Source: vulncheck.com
How do I fix CVE-2026-128332?
Upgrade to listmonk 7.0.0-beta.2 or later, which is the fixed version listed for this vulnerability.Source: vulncheck.com