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.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.12.13
- Who is exposed
- Not reported
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.
Written by a model
Original 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.
Who should check
Teams running SOGo before 5.12.13, particularly those with accounts that do not have TOTP enabled.
“SOGo before 5.12.13 contains an improper restriction”
What to do
Upgrade to a fixed version: 5.12.13.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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-13):
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"}.Affected versions
- Alinto sogofixed in 5.12.13
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now1 day
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Public exploit activity
- EPSS: 0.39%
- Posted on X by cve.now Nov 12
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-127111 |
| Record | NVD · CVE-2026-127111 |
| Other links 2 | |
| Patch | GitHub · Alinto/sogo · Release SOGo-5.12.13 |
| Link | vulncheck.com · advisories/sogo-before-unauthenticated-password-recovery-brute-force |
Questions about CVE-2026-127111
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: cve.now feed data
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: vulncheck.com
Which versions are affected by CVE-2026-127111?
sogo: before 5.12.13.
Source: cve.now feed data
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: vulncheck.com
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: vulncheck.com
Related
- CVE-2026-127131SOGo before 5.12.13 Missing Rate Limiting on TOTP Verification
- CVE-2026-93453SOGo before 5.12.11 Password Reset Token Interception via Origin Header
- CVE-2026-8851SOGo < 5.12.8 SQL Injection via addUserInAcls endpoint
- CVE-2026-130066Alinto SOGo before 5.12.13 SQL Injection via SQLSource Contact Lookup
- CVE-2026-127141SOGo before 5.12.13 Denial of Service via Auxiliary IMAP Account Greeting Wait
- CVE-2026-127121SOGo before 5.12.13 S/MIME Certificate Spoofing via UIxMailView
No corrections so far. Something wrong on this page? Report an error.