CVE-2026-112000

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

GHSA-93jv-pwc6-2cqf ↗EUVD-2026-103453 ↗

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.
vanus-labs vanus >= 0.8.0, <= 0.9.0
ETK-2026-2156Zero's internal tracking ID, independent of the CVE number., permanent identifier
18h 38msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+47h31m
0
+2h
+4h
+6h
+8h
+10h

description

Vanus gateway versions 0.8.0 through 0.9.0 fail to enforce authorization for certain subscription and unregistered method calls. An authenticated user may access another tenant's subscription data, acknowledge its events, disrupt its consumer, or enumerate users.

mitigation

Restrict gateway access to trusted, tenant-scoped accounts and revoke unnecessary credentials. Upgrade to a vendor release confirmed to be outside the affected range when one is available.

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.29%20th percentile
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-18 11:38Z
Δ 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-18 11:38Z
    ghsa: trigger signal, started the run
  2. 2026-10-18 11:38Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2156",
  "cve_id": "CVE-2026-112000",
  "display_id": "CVE-2026-112000",
  "ghsa_id": "GHSA-93jv-pwc6-2cqf",
  "euvd_id": "EUVD-2026-103453",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing gateway authorization in Vanus",
  "summary": "Vanus gateway versions 0.8.0 through 0.9.0 fail to enforce authorization for certain subscription and unregistered method calls. An authenticated user may access another tenant's subscription data, acknowledge its events, disrupt its consumer, or enumerate users.",
  "mitigation": "Restrict gateway access to trusted, tenant-scoped accounts and revoke unnecessary credentials. Upgrade to a vendor release confirmed to be outside the affected range when one is available.",
  "vendor": "vanus-labs",
  "product": "vanus",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.8.0, <= 0.9.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "vanus",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L",
  "epss_score": 0.0029,
  "epss_percentile": 0.2018,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.5625712,
  "t0_at": "2026-10-18T11:38:25.755000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-18T11:38:25.755000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-18T11:38:25.755000+00:00",
      "url": "https://github.com/advisories/GHSA-93jv-pwc6-2cqf"
    }
  }
}

published 2026-10-20 10:50Z
last change 2026-10-21 00:18Z

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.