CVE-2026-17362

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

GHSA-3mvj-682g-p7pp ↗EUVD-2026-118598 ↗

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 API Connect V12 OnPrem >= 12.1.0.0, <= 12.1.1.2
CWE-862 Missing Authorization
ETK-2026-3784Zero's internal tracking ID, independent of the CVE number., permanent identifier
18h 22msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h23m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

IBM API Connect V12 OnPrem 12.1.0.0 through 12.1.1.2 does not properly enforce authorization for tenant-management operations. A remote unauthenticated attacker can create, alter, or remove tenants when they can reach an affected deployment.

mitigation

Upgrade API Connect V12 OnPrem to version 12.1.1.3 or later. Until upgraded, restrict network access to the affected management interfaces to trusted administrators.

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.
–
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-07 03:25Z
Δ 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-07 03:25Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3784",
  "cve_id": "CVE-2026-17362",
  "display_id": "CVE-2026-17362",
  "ghsa_id": "GHSA-3mvj-682g-p7pp",
  "euvd_id": "EUVD-2026-118598",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization in API Connect V12 OnPrem tenant management",
  "summary": "IBM API Connect V12 OnPrem 12.1.0.0 through 12.1.1.2 does not properly enforce authorization for tenant-management operations. A remote unauthenticated attacker can create, alter, or remove tenants when they can reach an affected deployment.",
  "mitigation": "Upgrade API Connect V12 OnPrem to version 12.1.1.3 or later. Until upgraded, restrict network access to the affected management interfaces to trusted administrators.",
  "vendor": "IBM",
  "product": "API Connect V12 OnPrem",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 12.1.0.0, <= 12.1.1.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "API Connect V12 OnPrem",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.55443985,
  "t0_at": "2026-11-07T03:25:11.041000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-07T03:25:11.041000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-07T03:25:11.041000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-17362"
    }
  }
}

published 2026-11-07 03:34Z
last change 2026-11-08 00:40Z

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.