# CVE-2026-128332: listmonk 6.0.0 before 7.0.0-beta.2 TOTP Brute-Force via /admin/login/twofa


- **Severity:** Critical 9.1 (`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 in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-p42g-4rv2-xg2f

## What is CVE-2026-128332?

CVE-2026-128332 is a critical vulnerability in knadh listmonk, published on 13 Nov 2026. 

### Official description

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.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

1 open source package ship an affected version, including github.com/knadh/listmonk.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `github.com/knadh/listmonk` | Go | `pkg:golang/github.com/knadh/listmonk` | From 6.0.0 | 7.0.0-beta.2 |

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

Upgrade github.com/knadh/listmonk to 7.0.0-beta.2 or later.

## Is CVE-2026-128332 being exploited?

There is no known exploitation of CVE-2026-128332 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128332 and fix it if it is affected.

What it is: CVE-2026-128332 is a critical vulnerability in knadh listmonk, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128332 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/knadh/listmonk (Go): affected from 6.0.0; fixed in 7.0.0-beta.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128332/ (Markdown: https://insights.sbomify.com/CVE-2026-128332/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128332
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128332
- OSV: https://osv.dev/vulnerability/CVE-2026-128332

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128332/
Summaries are generated and may contain mistakes; the official description above is the record.
