CVE-2026-117545

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

GHSA-6vp2-3r79-77x4 ↗EUVD-2026-119682 ↗

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 webMethods Integration Server 12.1
CWE-287 Improper Authentication
ETK-2026-3905Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 08h 22msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+29h18m
0
+2h
+4h
+6h
+8h
+10h

description

IBM webMethods Integration Server 12.1 is affected by an authentication-related access-control bypass. An attacker with remote authenticated access may be able to evade security restrictions; obtaining valid authenticated access is a prerequisite.

mitigation

Restrict remote access to trusted networks and reduce privileges for Integration Server accounts. Monitor IBM guidance and apply the vendor-provided corrected release when it becomes 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.37%30th percentile
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-08 17:06Z
Δ 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:06Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3905",
  "cve_id": "CVE-2026-117545",
  "display_id": "CVE-2026-117545",
  "ghsa_id": "GHSA-6vp2-3r79-77x4",
  "euvd_id": "EUVD-2026-119682",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in IBM webMethods Integration Server",
  "summary": "IBM webMethods Integration Server 12.1 is affected by an authentication-related access-control bypass. An attacker with remote authenticated access may be able to evade security restrictions; obtaining valid authenticated access is a prerequisite.",
  "mitigation": "Restrict remote access to trusted networks and reduce privileges for Integration Server accounts. Monitor IBM guidance and apply the vendor-provided corrected release when it becomes available.",
  "vendor": "IBM",
  "product": "webMethods Integration Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "12.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "webMethods Integration Server",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0037,
  "epss_percentile": 0.307,
  "epss_asof": "2026-11-09",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.414713566666666,
  "t0_at": "2026-11-08T17:06:33.709000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-08T17:06:33.709000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T17:06:33.709000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-117545"
    }
  }
}

published 2026-11-08 17: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.