Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

SOGo TOTP Rate Limit Flaw (CVE-2026-127131)

CVE-2026-127131 is a missing rate limit in SOGo's web login TOTP verification.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-127131
Vendor
Alinto
Affected Product
SOGo web login with TOTP
Exploitation
Not confirmed
Published
2026-11-12

The CVE record says an attacker must already know the account password before attempting to guess the second factor.Failed TOTP entries do not increment the failed-login counter, according to the VulnCheck CVE record. The configured maximum failed-login count therefore does not stop repeated code guesses. The record rates the flaw CVSS 4.0 9.1 Critical and CVSS 3.1 7.4 High.

What it allows

How Does CVE-2026-127131 Bypass SOGo TOTP?

The password step must succeed first. The CVE record says wrong TOTP codes leave SOGo's failed-login counter unchanged, so its maximum failed-login setting does not constrain this stage.

An attacker with a valid password can keep guessing second-factor codes over successive code windows. A successful guess could open the account despite its multi-factor authentication setting. The record does not describe a password bypass or a way to learn the password.

What Does the Current Evidence Mean for Risk?

The prerequisite makes accounts with exposed or reused passwords the immediate concern. Brandefense Blackhole counted two dark-chat posts matching this CVE from August 14 to November 12, 2026. The measured unit is posts, not incidents or affected accounts.

Those posts are research signals and do not establish active exploitation. As a defender precaution, prioritize internet-reachable SOGo instances with TOTP enabled and investigate unusual login activity. For related product context, see the vulnerability intelligence platform page.

Who is affected

Which SOGo Versions Are Affected?

The VulnCheck CVE record lists Alinto SOGo versions before 5.12.13 as affected. Its described condition is web login using TOTP; the record does not identify a narrower operating system or deployment package.

Alinto announced 5.12.13 on November 4, 2026 and urged users of earlier versions to update. Its release page discusses several security fixes but does not explicitly map the TOTP flaw to a release-note item. Check the installed SOGo version against the vendor release and package maintainer's security update.

How Should Defenders Verify the Fix?

Upgrade affected SOGo deployments to 5.12.13 or a later supported security release. After restarting each SOGo instance, use the Version API in Alinto's installation guide to read its running major, minor and patch values. Confirm 5.12.13 or a later supported release on every instance; an installed package version alone does not prove the process restarted.

Review authentication logs for sustained wrong TOTP entries after correct passwords, then investigate any unexpected successful session. This is a Brandefense detection recommendation, not a claim of observed attacks. Use a patch management process to record the upgrade and the post-change check.

Timeline

  1. 2026-11-04

    Alinto announced SOGo 5.12.13 with security fixes. The release announcement did not identify this TOTP CVE by number.

  2. 2026-11-12

    VulnCheck published the CVE record describing missing TOTP attempt limits and versions before 5.12.13.

What to do

  1. Inventory SOGo and TOTP exposure

    Identify web login deployments using TOTP and record each running SOGo version. Prioritize internet-reachable deployments and accounts whose passwords may have been exposed.

  2. Apply the SOGo security release

    Update versions before 5.12.13 to 5.12.13 or a later supported security release. Follow the vendor and package maintainer's update path.

  3. Verify the running version

    Restart each SOGo instance, read its running version with Alinto's documented Version API, and record that every instance reports 5.12.13 or later.

  4. Review authentication telemetry

    Investigate repeated wrong TOTP entries after correct passwords and unexpected successful sessions. Treat these as investigation leads, not independent proof of exploitation.

What Brandefense can do

Frequently Asked Questions

What does CVE-2026-127131 allow?

An attacker who already knows a valid password may repeatedly guess a SOGo web login TOTP code. The CVE record says failed second-factor attempts do not trigger the failed-login limit.

Can the flaw bypass the password step?

No. The VulnCheck CVE record explicitly requires the attacker to possess the account password before guessing the TOTP code.

Which SOGo version addresses this flaw?

The CVE record marks versions before 5.12.13 as affected. Alinto announced 5.12.13 with security fixes on November 4, 2026; verify the running version after updating.

Does Brandefense Blackhole activity prove exploitation?

No. Two matching dark-chat posts were counted from August 14 to November 12, 2026. Posts are research signals, not verified attacks or affected accounts.

Sources

  1. CVE-2026-127131 recordVulnCheck CNA via CVE Program
  2. SOGo v5.12.13 releasedAlinto
  3. SOGo Installation and Configuration GuideAlinto
  4. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →