Auth bypass flaws in YunoHost SOGo app
Free public brief. The indicators, the detections with Splunk and KQL already written, and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Two vulnerabilities in the YunoHost sogo_yhn package let unauthenticated attackers log in as any user, including admins, without a valid password.
CERT Polska coordinated disclosure of two authentication bypass vulnerabilities in the sogo_yhn YunoHost application package, which configures the SOGo groupware server. CVE-2026-74864 stems from sogo_yhn configuring SOGo to trust the 'x-webobjects-remote-user' HTTP header as proof of authentication; because Nginx does not strip this header, any client can set it arbitrarily and impersonate any user, including privileged accounts, with no password required. CVE-2026-74865 arises from the 'SOGoTrustProxyAuthentication=YES' setting, which causes HTTP Basic authentication to skip password verification entirely — an attacker who knows only a valid username can log in as that user with any password value.
Both issues represent complete authentication bypass on affected SOGo/YunoHost deployments, allowing full account takeover including administrative access, without requiring any prior credentials or user interaction. There is no indication in the report of in-the-wild exploitation; this is a coordinated, responsibly disclosed report credited to Przemysław Knycz (WeKrwi.IT).
The vulnerabilities were fixed in sogo_yhn version 5.8.0~ynh9. Defenders running YunoHost with the sogo_yhn app should upgrade immediately to this or a later version, and audit SOGo/Nginx proxy configurations to ensure the x-webobjects-remote-user header is stripped or not trusted from untrusted network paths, and that SOGoTrustProxyAuthentication is not enabled unless the environment strictly requires and secures proxy-based authentication.
Mentioned in this report
Source reporting: https://cert.pl/en/posts/2026/09/CVE-2026-74864
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections with the Splunk SPL and Microsoft KQL already written, the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 11,423 reports from 154 sources, 2,072 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs