External risk intelligence

SOGo Missing Rate Limiting on TOTP Verification

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-127131

SOGo is a collaborative software suite providing webmail and groupware functionality. As a gateway for email and identity services, its login endpoints are designed to be public-facing to enable remote access for users, making the web login interface a primary and intended internet-facing service.

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in SOGo's web login allows attackers to bypass two-factor authentication if they already have a user's password. This issue could potentially allow unauthorized access to accounts.

  • Bypasses two-factor login if password is known.
  • Affects systems enabling remote access.
  • Confirm if SOGo is used and if accounts have lost passwords.

Attack Path

How an attacker could exploit the issue

An attacker who already knows a victim's password can repeatedly guess the two-factor authentication code without being blocked. This is possible because the system doesn't track failed second-factor attempts, allowing attackers to try many codes quickly until they find the correct one and gain access to the account.

  • Attacker possesses victim's password.
  • Repeatedly submit TOTP codes.
  • Bypass two-factor authentication.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker who already possesses a victim's password could repeatedly guess the second-factor authentication code, bypassing two-factor authentication by exploiting a missing rate limit on TOTP verification.

  • User credentials could be compromised.
  • Attackers could brute-force verification codes.
  • Unauthorized account access may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability likely impacts organizations using SOGo for their email and groupware services, making the platform or application support teams responsible for assessing and mitigating the risk. The first practical step is to inventory all SOGo instances, determine their internet exposure and business criticality, and identify the accountable owner for each deployment before planning remediation.

  • Identify SOGo deployment owners.
  • Verify internet exposure and criticality.
  • Plan remediation based on exposure.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is SOGo and how is it used?

SOGo is a collaborative software suite used by organizations to provide web-based email, calendar, and address book functionality. It serves as a central hub for identity and communication services, allowing users to access their professional data remotely through a web browser.

What does CVE-2026-127131 mean by missing rate limiting?

This vulnerability, classified as CWE-307: Improper Restriction of Excessive Authentication Attempts, means the application fails to restrict how many times a user can guess a 2FA code. While most systems lock an account after a few failed attempts, SOGo ignores these failures during TOTP verification, allowing for unlimited guesses.

How does an attacker trigger this vulnerability?

An attacker must first possess the victim's valid password. Once they have those credentials, they can repeatedly submit various TOTP codes against the /SOGo/connect endpoint. If the user does not have 2FA enabled, this specific mechanism is not triggered; the bug relies entirely on the absence of a failure counter for second-factor codes.

Is my SOGo instance at risk?

According to Halo Surface Signal, because SOGo is designed as a gateway for remote email and groupware access, its login endpoints are frequently internet-facing. If your instance is accessible from the internet to support remote workers, it is in a position where external attackers could attempt to exploit this login weakness.

What should I do to address this CVE?

The immediate priority is to locate all SOGo deployments within your environment and identify who owns or manages them. Once you have an inventory of these systems, assess whether they are reachable from the public internet. You should then coordinate with the system administrators to plan for an update to version 5.12.13 or newer to close this gap.

References