CVE-2026-18093

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

GHSA-x2fm-49wv-jv8m ↗EUVD-2026-119712 ↗

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.
IBM App Connect Enterprise >= 13.0.1.0, <= 13.0.8.2
CWE-863 Incorrect Authorization
ETK-2026-3907Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 11h 32msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+25h35m
0
+2h
+4h
+6h
+8h
+10h

description

IBM App Connect Enterprise 13.0.1.0 through 13.0.8.2 is affected by an authorization flaw. An unauthenticated attacker who can reach an affected deployment may access sensitive information.

mitigation

Restrict network access to affected App Connect Enterprise deployments to trusted users and management networks. Monitor IBM guidance and apply a vendor-provided update when a fixed release is identified.

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.49%42nd percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-08 17:52Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-08 17:52Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3907",
  "cve_id": "CVE-2026-18093",
  "display_id": "CVE-2026-18093",
  "ghsa_id": "GHSA-x2fm-49wv-jv8m",
  "euvd_id": "EUVD-2026-119712",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Broken access control in IBM App Connect Enterprise",
  "summary": "IBM App Connect Enterprise 13.0.1.0 through 13.0.8.2 is affected by an authorization flaw. An unauthenticated attacker who can reach an affected deployment may access sensitive information.",
  "mitigation": "Restrict network access to affected App Connect Enterprise deployments to trusted users and management networks. Monitor IBM guidance and apply a vendor-provided update when a fixed release is identified.",
  "vendor": "IBM",
  "product": "App Connect Enterprise",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 13.0.1.0, <= 13.0.8.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "App Connect Enterprise",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0049,
  "epss_percentile": 0.4231,
  "epss_asof": "2026-11-09",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.11282825,
  "t0_at": "2026-11-08T17:52:22.839000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-08T17:52:22.839000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T17:52:22.839000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-18093"
    }
  }
}

published 2026-11-08 18:24Z
last change 2026-11-11 05:47Z

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.