CVE-2026-111999

validatingZero is analyzing and reversing it now.

EUVD-2026-103452 ↗

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
CWE-306 Missing Authentication for Critical Function
ETK-2026-1971Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Vanus 0.8.0 through 0.9.0 does not enforce publisher authentication for event submission through its gateway HTTP CloudEvents receiver. An unauthenticated remote party that can reach the receiver can inject events into event buses, where they may be forwarded to configured subscribers.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Restrict network access to the Vanus gateway HTTP receiver to trusted clients and block untrusted access to its event-publication routes. Upgrade to a vendor-provided corrected release when one is identified; no fixed version is recorded in the advisory.

check
building now
exploit
not yet
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.
–
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.53%43rd percentile
agent run time
12m
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

Run in progress: no artifact yet.

source signals

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

  1. 2026-10-18 11:38Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1971",
  "cve_id": "CVE-2026-111999",
  "display_id": "CVE-2026-111999",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-103452",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Missing authentication in Vanus gateway event publishing",
  "summary": "Vanus 0.8.0 through 0.9.0 does not enforce publisher authentication for event submission through its gateway HTTP CloudEvents receiver. An unauthenticated remote party that can reach the receiver can inject events into event buses, where they may be forwarded to configured subscribers.",
  "mitigation": "Restrict network access to the Vanus gateway HTTP receiver to trusted clients and block untrusted access to its event-publication routes. Upgrade to a vendor-provided corrected release when one is identified; no fixed version is recorded in the advisory.",
  "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": [
    306
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0053,
  "epss_percentile": 0.4387,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.832365283333333,
  "t0_at": "2026-10-18T11:38:25.071000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-18T11:38:25.071000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-18T11:38:25.071000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111999"
    }
  }
}

published 2026-10-18 12:52Z
last change 2026-10-21 15:05Z

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.