CVE-2026-118904

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

GHSA-rx5h-4548-3rqv ↗EUVD-2026-119748 ↗

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-3914Zero's internal tracking ID, independent of the CVE number., permanent identifier
2d 08h 12msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h45m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

IBM webMethods Integration Server 12.1 is affected by an improper-authentication flaw. A remote attacker with valid authentication may be able to circumvent security restrictions.

mitigation

Restrict access to the server to trusted users and networks, and review account privileges. Monitor IBM security guidance and apply the vendor-provided update 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.32%25th percentile
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-08 19:48Z
Δ 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 19:48Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3914",
  "cve_id": "CVE-2026-118904",
  "display_id": "CVE-2026-118904",
  "ghsa_id": "GHSA-rx5h-4548-3rqv",
  "euvd_id": "EUVD-2026-119748",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authentication in IBM webMethods Integration Server",
  "summary": "IBM webMethods Integration Server 12.1 is affected by an improper-authentication flaw. A remote attacker with valid authentication may be able to circumvent security restrictions.",
  "mitigation": "Restrict access to the server to trusted users and networks, and review account privileges. Monitor IBM security guidance and apply the vendor-provided update 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.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0032,
  "epss_percentile": 0.2557,
  "epss_asof": "2026-11-09",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.768977683333333,
  "t0_at": "2026-11-08T19:48:22.159000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-08T19:48:22.159000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T19:48:22.159000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-118904"
    }
  }
}

published 2026-11-08 19:54Z
last change 2026-11-11 05:12Z

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.