Quick answers
- Is CVE-2026-127131 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-127131 being exploited in the wild.
- How severe is CVE-2026-127131?
- High severity, with a CVSS score of 7.4, published 12 November 2026.
- Which products and versions are affected?
- Alinto Sogo before 5.12.13.
- Is there a fix for CVE-2026-127131?
- Yes: fixed in 5.12.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-127131 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-127131?
- Check whether you run Alinto Sogo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 5.12.13
Technical details
The vulnerability exists in the /SOGo/connect login endpoint where failed TOTP verification attempts do not increment the failed-login counter, causing SOGoMaximumFailedLoginCount policy to never apply. An unauthenticated attacker with a valid password can send unlimited POST requests with varying TOTP codes across 30-second code windows, enabling practical brute-force attacks against the second factor. The issue is fixed in SOGo 5.12.13.
Affected products
- Alinto SOGo before 5.12.13
Timeline
- 2026-11-12: disclosed
- 2026-11-04: patched: SOGo 5.12.13 released