cve.bz

CVE-2026-127111 SOGo before 5.12.13 Unauthenticated Password Recovery Brute Force

9.1 criticalEPSS 0.3%

Critical (9.1) in alinto sogo. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

9.1 critical
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

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-307 Improper Restriction of Excessive Authentication Attempts
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-127111 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-127111?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-127111?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-127111 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-127111

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-127111](https://cve.bz/cve/badge/CVE-2026-127111.svg)](https://cve.bz/cve/CVE-2026-127111)

HTML:

<a href="https://cve.bz/cve/CVE-2026-127111"><img src="https://cve.bz/cve/badge/CVE-2026-127111.svg" alt="CVE-2026-127111"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Alinto sogobefore 5.12.13

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13sogono fix listedDEBIAN-CVE-2026-127111
Ubuntu26.10, Pro:16.04:LTS, Pro:18.04:LTS and 3 moresogono fix listedUBUNTU-CVE-2026-127111

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-16 Dictionary-based Password Attack Likelihood: Medium · Severity: High
  • CAPEC-49 Password Brute Forcing Likelihood: Medium · Severity: High
  • CAPEC-560 Use of Known Domain Credentials Likelihood: High · Severity: High
  • CAPEC-565 Password Spraying Likelihood: High · Severity: High
  • CAPEC-600 Credential Stuffing Likelihood: High · Severity: High
  • CAPEC-652 Use of Known Kerberos Credentials Likelihood: Medium · Severity: High
  • CAPEC-653 Use of Known Operating System Credentials Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON