Authentication Bypass in sogo_yhn

Answer in brief

CVE-2026-74864 records a Critical severity (CVSS 9.3) vulnerability in Authentication Bypass in sogo_yhn. The current sources do not mark it as known exploited. The current feed maps YunoHost-Apps/sogo_yhn (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 30, 2026Updated Sep 30, 2026Source checked Sep 30, 2026First seen by HOL Sep 30, 2026Material review Sep 30, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 9.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 9.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps YunoHost-Apps/sogo_yhn (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
YunoHost-Apps/sogo_yhngeneric	>=0 <5.8.0~ynh9	5.8.0~ynh9

Recommended response

Check inventory. Check lockfiles and deployed manifests for YunoHost-Apps/sogo_yhn.
Review the reported fix. Update YunoHost-Apps/sogo_yhn to 5.8.0~ynh9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 30, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.