Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-33550: CWE-308 Use of Single-factor Authentication in Alinto SOGo

0
Low
VulnerabilityCVE-2026-33550cvecve-2026-33550cwe-308
Published: Sun Mar 22 2026 (03/22/2026, 02:16:56 UTC)
Source: CVE Database V5
Vendor/Project: Alinto
Product: SOGo

Description

CVE-2026-33550 is a low-severity vulnerability in Alinto's SOGo email and collaboration platform versions before 5. 12. 5. The issue involves improper handling of one-time passwords (OTPs) used for multi-factor authentication (MFA). Specifically, when a user disables and then re-enables OTP-based MFA, the system fails to renew the OTP secret, and the OTP length is only 12 digits instead of the recommended 20 digits. This weakness effectively reduces the strength of the second authentication factor, increasing the risk of unauthorized access through OTP guessing or replay attacks. Exploitation requires high privileges and user interaction, and no known exploits exist in the wild. Organizations using vulnerable SOGo versions should upgrade to 5. 12. 5 or later and enforce stronger OTP configurations to mitigate this risk.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/29/2026, 20:10:20 UTC

Technical Analysis

CVE-2026-33550 addresses a security vulnerability in Alinto's SOGo collaboration suite prior to version 5.12.5, related to the implementation of OTP-based multi-factor authentication. The vulnerability arises because the system does not renew the OTP secret when a user disables and then re-enables OTP MFA, meaning the same OTP secret remains active. Additionally, the OTP length is limited to 12 digits, which is significantly shorter than the recommended 20-digit length for robust security. This combination weakens the second factor's effectiveness, potentially allowing attackers to guess or replay OTPs more easily. The vulnerability is classified under CWE-308, indicating the use of single-factor authentication or weak multi-factor authentication mechanisms. The CVSS v3.1 base score is 2.0, reflecting low severity due to the requirement of high privileges (PR:H), user interaction (UI:R), and high attack complexity (AC:H). The vulnerability does not impact confidentiality but can lead to integrity loss if an attacker successfully bypasses MFA. No known exploits have been reported, and no patches are explicitly linked, but upgrading to version 5.12.5 or later is advised. This vulnerability highlights the importance of proper OTP lifecycle management and adherence to recommended OTP length standards to maintain strong authentication security.

Potential Impact

The primary impact of this vulnerability is a reduction in the security strength of the multi-factor authentication mechanism in SOGo, potentially allowing attackers with sufficient privileges and user interaction to bypass or weaken the second authentication factor. This could lead to unauthorized access to user accounts, compromising the integrity of email and collaboration data. While confidentiality and availability are not directly affected, unauthorized account access can facilitate further attacks such as phishing, data manipulation, or lateral movement within an organization. The low CVSS score and lack of known exploits suggest limited immediate risk, but organizations relying on SOGo for secure communications could face increased risk if attackers exploit this weakness in OTP management. The impact is more pronounced in environments where SOGo is a critical communication platform and where MFA is relied upon heavily for securing user access.

Mitigation Recommendations

Organizations should upgrade Alinto SOGo to version 5.12.5 or later, where this vulnerability is addressed. Administrators must ensure that OTP secrets are properly renewed whenever users disable and re-enable MFA to prevent reuse of old OTP secrets. Increasing the OTP length to at least the recommended 20 digits will significantly enhance the security of the second factor. Additionally, organizations should audit their MFA configurations to verify compliance with best practices, including enforcing strong OTP generation parameters and monitoring for unusual authentication patterns. User education on the importance of MFA and cautious handling of authentication settings can further reduce risk. Implementing additional layers of security such as device-based authentication or hardware tokens may also help mitigate risks associated with weak OTP implementations.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-03-22T02:16:55.848Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69bf545af4197a8e3b1d674e

Added to database: 3/22/2026, 2:30:50 AM

Last enriched: 3/29/2026, 8:10:20 PM

Last updated: 5/7/2026, 4:31:52 AM

Views: 100

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses