CVE
SOGo denial of service via auxiliary IMAP account greeting wait
SOGo before 5.12.13 is affected when an auxiliary IMAP mail account points to a host that accepts TCP but never sends an IMAP greeting. Fixed in 5.12.13.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.12.13
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. SOGo before 5.12.13 An auxiliary IMAP mail account is configured to point to a controlled host that accepts TCP but never sends an IMAP greeting
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.29% · 21st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
SOGo, from Alinto, is affected. An attacker with a low-privilege logged-in account can remotely configure an auxiliary IMAP account pointing to a host that accepts connections but never sends a greeting, then send concurrent requests to hold every worker process and deny service to all users for about five minutes.
Read the original description
SOGo before 5.12.13 contains a denial of service vulnerability that allows authenticated attackers to exhaust all worker processes by configuring an auxiliary IMAP mail account pointing to a controlled host that accepts a TCP connection but never sends an IMAP greeting response. Attackers can issue concurrent GET requests to the mail view of this account to hold workers indefinitely without an effective timeout, occupying every SOGo worker and denying service to all users for approximately five minutes until the watchdog kills and respawns the stuck workers.
Who should check
Teams running SOGo before 5.12.13 where users can configure auxiliary IMAP mail accounts.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
SOGo before 5.12.13 An auxiliary IMAP mail account is configured to point to a controlled host that accepts TCP but never sends an IMAP greetingUpgrade 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-127141 (SOGo before 5.12.13 Denial of Service via Auxiliary IMAP Account Greeting Wait), 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-127141 (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 before 5.12.13 (source: https://www.vulncheck.com/advisories/sogo-before-denial-of-service-via-auxiliary-imap-account-greeting-wait)
- An auxiliary IMAP mail account is configured to point to a controlled host that accepts TCP but never sends an IMAP greeting (source: https://www.vulncheck.com/advisories/sogo-before-denial-of-service-via-auxiliary-imap-account-greeting-wait)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-127141 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127141 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-denial-of-service-via-auxiliary-imap-account-greeting-wait
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-127141
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-127141"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Alinto sogo
fixed in 5.12.13
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-127141
Is CVE-2026-127141 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 authenticated attacker can exhaust all SOGo worker processes, denying service to all users for about five minutes until the watchdog respawns them.Source: vulncheck.com
Which versions are affected by CVE-2026-127141?
sogo: before 5.12.13.Source: cve.now feed data
Am I affected, and how do I check?
Versions before 5.12.13 are affected, and the setup involves an auxiliary IMAP mail account configured to point to a host that accepts TCP but never sends an IMAP greeting. Check the installed SOGo version and the auxiliary IMAP account settings.Source: vulncheck.com
How do I fix CVE-2026-127141?
Upgrade SOGo to 5.12.13, the fixed version.Source: vulncheck.com