CVE-2026-108853

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

GHSA-fg7x-9rxv-3m3p ↗EUVD-2026-97004 ↗

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.
UnicomAI Wanwu < 0.6.3
fixed in 0.6.3
ETK-2026-1258Zero's internal tracking ID, independent of the CVE number., permanent identifier
9d 10h 20msince last run
1h 23mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+6h
0
+2h
+4h
+8h
+10h
+12h

description

UnicomAI Wanwu versions before 0.6.3 do not adequately enforce tenant authorization when deleting applications. An authenticated user with limited privileges may delete applications belonging to other tenants, along with related workflows, conversations, and data.

mitigation

Upgrade UnicomAI Wanwu to version 0.6.3 or later. Until upgraded, restrict low-privileged user access and monitor application-deletion activity.

fixed in 0.6.3

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.30%21st percentile
agent run time
1h 23m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-11 13:26Z
Δ 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-10-11 13:26Z
    ghsa: trigger signal, started the run
  2. 2026-10-11 13:26Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1258",
  "cve_id": "CVE-2026-108853",
  "display_id": "CVE-2026-108853",
  "ghsa_id": "GHSA-fg7x-9rxv-3m3p",
  "euvd_id": "EUVD-2026-97004",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-tenant object access flaw in UnicomAI Wanwu",
  "summary": "UnicomAI Wanwu versions before 0.6.3 do not adequately enforce tenant authorization when deleting applications. An authenticated user with limited privileges may delete applications belonging to other tenants, along with related workflows, conversations, and data.",
  "mitigation": "Upgrade UnicomAI Wanwu to version 0.6.3 or later. Until upgraded, restrict low-privileged user access and monitor application-deletion activity.",
  "vendor": "UnicomAI",
  "product": "Wanwu",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.6.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.6.3"
      ],
      "package_name": "Wanwu",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
  "epss_score": 0.003,
  "epss_percentile": 0.2149,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 83.13013681666666,
  "t0_at": "2026-10-11T13:26:02.706000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-11T13:26:02.706000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T13:26:02.706000+00:00",
      "url": "https://github.com/advisories/GHSA-fg7x-9rxv-3m3p"
    }
  }
}

published 2026-10-11 18:03Z
last change 2026-10-21 05:31Z

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.