CVE-2026-74864

waiting for further signalsZero needs more public information before it can validate it.

GHSA-fxx9-8vhm-fwhc ↗EUVD-2026-89796 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
YunoHost-Apps sogo_yhn < 5.8.0~ynh9
fixed in 5.8.0~ynh9
CWE-639 Authorization Bypass Through User-Controlled Key
ETK-2026-110, permanent identifier
19d 09h 23msince last run
28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+32h41m
0
+2h
+4h
+6h
+8h
+10h

description

Affected sogo_yhn deployments may accept a client-supplied identity header as authenticated, bypassing password checks. An attacker able to send requests through the affected Nginx path could impersonate arbitrary accounts, including privileged ones.

mitigation

Upgrade sogo_yhn to version 5.8.0~ynh9 or later. Until upgraded, restrict access to the service and ensure untrusted clients cannot supply the identity header.

fixed in 5.8.0~ynh9

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.41%33rd percentile
agent run time
28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 12:02Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-30 12:02Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-74864

{
  "etk_id": "ETK-2026-110",
  "cve_id": "CVE-2026-74864",
  "display_id": "CVE-2026-74864",
  "ghsa_id": "GHSA-fxx9-8vhm-fwhc",
  "euvd_id": "EUVD-2026-89796",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Header-based authentication bypass in sogo_yhn",
  "summary": "Affected sogo_yhn deployments may accept a client-supplied identity header as authenticated, bypassing password checks. An attacker able to send requests through the affected Nginx path could impersonate arbitrary accounts, including privileged ones.",
  "mitigation": "Upgrade sogo_yhn to version 5.8.0~ynh9 or later. Until upgraded, restrict access to the service and ensure untrusted clients cannot supply the identity header.",
  "vendor": "YunoHost-Apps",
  "product": "sogo_yhn",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 5.8.0~ynh9"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "5.8.0~ynh9"
      ],
      "package_name": "sogo_yhn",
      "purl": null
    }
  ],
  "cwes": [
    639
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0041,
  "epss_percentile": 0.3352,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.427899766666666,
  "t0_at": "2026-09-30T12:02:29.340000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T12:02:29.340000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T12:02:29.340000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-74864"
    }
  }
}

published 2026-09-30 13:05Z
last change 2026-10-21 06:02Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.