# CVE-2026-107145: Lack of rate-limiting in 2fa code check mechanism in twofactor_gauthenticator


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-j947-85xj-mvc2, UBUNTU-CVE-2026-107145

## What is CVE-2026-107145?

CVE-2026-107145 is a medium-severity vulnerability in alexandregz twofactor_gauthenticator, published on 27 Oct 2026. 

### Official description

The twofactor_gauthenticator plugin for Roundcube is vulnerable to brute-forcing of the second-factor code. Due to the lack of rate limiting, an attacker who obtains user's password can submit arbitrary 6-digit codes, resulting in second-factor bypass and unauthorized access to the system.

This issue was fixed in commit 4640889.

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

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


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

No fix has been published for CVE-2026-107145 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-107145 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107145 is a medium-severity vulnerability in alexandregz twofactor_gauthenticator, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-107145 in the wild and no public exploit code.

Affected product: alexandregz twofactor_gauthenticator. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-107145/ (Markdown: https://insights.sbomify.com/CVE-2026-107145/index.md)
```

## Sources

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

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