CVE-2026-74864: YunoHost-Apps sogo_yhn · Insecure Direct Object Reference
Affects YunoHost-Apps sogo_yhnSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 5.8.0~ynh9 as a priority.
Data as of 14 Nov 2026, 20:44 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.8.0~ynh9
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade YunoHost-Apps sogo_yhn to 5.8.0~ynh9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| YunoHost-Appssogo_yhn | Affected
| Fixed in
|
GitHubsogo_yhnpkg:github/sogo_yhnOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade sogo_yhn to version 5.8.0~ynh9 or later, where this vulnerability has been fixed. Until then, consider implementing controls to strip or block the "x-webobjects-remote-user" header at the web server or proxy level to prevent unauthorized header injection.
Description
sogo_yhn configures SOGo with a parameter that forces the request with HTTP header "x-webobjects-remote-user" to be treated as sent by a verified user without performing password validation. Since Nginx does not strip this header, any client can supply it arbitrarily and gain access as any user, including a privileged user, without providing a password. This issue was fixed in version 5.8.0~ynh9.