On this page (7 sections)

A critical vulnerability, CVE-2026-114464, has been published for IBM Process Mining versions 2.0.0 through 2.2.1. The GitHub Advisory Database entry says a remote attacker could obtain sensitive information because access to a resource is not properly restricted.

If your organization runs IBM Process Mining, particularly on a network that other systems or users can reach, confirm your version and read IBM's bulletin now. Public detail is thin, so this article separates what is confirmed from what is not.

What was disclosed

The public description is a single sentence covering the affected range, the outcome (disclosure of sensitive information) and the cause (improper access control). The record was published on November 8, 2026, and IBM's own page is listed as a reference at ibm.com/support/pages/node/7294875. The NVD entry carries the same text, so it is not separate confirmation.

Only one independent publisher covers this so far, and the GitHub entry is marked unreviewed. Treat anything beyond the description as unverified until you have read IBM's bulletin.

Technical details

CWE-284, Improper Access Control, describes a product that does not restrict, or wrongly restricts, access to a resource from an unauthorized actor. In practice this is a missing or flawed permission check: a function, endpoint or data set that should require a certain role or login can be reached by someone who should not have access.

The CVSS v3.1 vector in the advisory is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N. In plain terms:

  • Attack vector Adjacent: the attacker needs to be on the same network segment or a closely connected network, not anywhere on the internet.
  • Attack complexity Low, no privileges required, no user interaction required.
  • Scope Changed: the impact can reach resources beyond the vulnerable component.
  • Confidentiality High and Integrity High, Availability None.
The description says a remote attacker, while the vector says Adjacent. The sources do not explain the difference, so do not assume the product is safe just because it is not internet-facing, and do not assume it is exposed to the whole internet either. The Integrity rating is also High even though the description mentions only information disclosure. IBM's bulletin should clarify both.

The sources do not say which Process Mining component or function is affected, and no exploit details appear in the material reviewed.

Who is affected

Any deployment of IBM Process Mining from 2.0.0 through 2.2.1 falls in the stated range. Process mining tools typically ingest event logs from business systems, so the data behind them may include operational and customer-related records. That is general context, not a statement from the advisory about what this flaw exposes.

Exposure depends on network placement. With an Adjacent attack vector, instances reachable from shared office networks, flat internal networks, VPN ranges or partner links deserve the most attention.

How to check your exposure

First confirm which version you run. The exact place differs by deployment, so check the product's about or version page in the administration interface, or your deployment records and image tags. Compare the result with 2.0.0 through 2.2.1.

Then work out who can reach the service. A review of firewall rules, security groups and load balancer listeners shows which networks can connect to it.

If the instance sits behind an nginx reverse proxy you control, this read-only command counts requests per client address in the access log, so you can spot unfamiliar networks. Run it on the proxy host and adjust the log path to your setup; the output lists the 20 busiest client addresses.

Count requests per client address in an nginx access log (run on the proxy host, adjust the path)Shell
awk '{print $1}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head -20

What to do now

  1. Identify every IBM Process Mining instance and record its version.
  2. Open IBM's page at https://www.ibm.com/support/pages/node/7294875 and follow its instructions for fixed versions or interim fixes. The fixed version is not stated in the research reviewed here.
  3. Apply the update or mitigation IBM provides, after testing in a staging environment where you can.
  4. Restrict network access to the service to the smallest set of hosts and users that need it, using firewall rules or segmentation.
  5. Review who holds accounts and what data sources feed the tool, and remove anything that is not needed.
  6. Check access logs for unfamiliar clients or unusual data retrieval since the instance was first reachable, and keep those logs.
  7. If you find signs of unauthorized access, treat credentials and secrets stored in or used by the tool as exposed and rotate them.
Caution. Upgrades and restarts of a business analytics platform can interrupt users and scheduled data imports. Plan a maintenance window and back up configuration and data first.

Detection and monitoring

No indicators of compromise appear in the sources reviewed, so detection relies on general hygiene. Watch for requests from addresses outside your expected networks, spikes in data export or API activity, and access to resources by accounts that normally never touch them. Forward application and proxy logs to a central place so they survive an incident.

For any web-facing part of your estate, regular checks of certificates, DNS and response headers help catch unexpected changes. Webforta Monitor covers uptime, certificate, DNS and header-change monitoring, though it does not assess this specific product. For guidance on handling a suspected compromise, see Website hacked: what to do.

What is still unknown

  • The fixed version or patch details (the GitHub entry lists patched versions as unknown).
  • Whether the flaw is being exploited. No exploitation is reported in the research, and no CISA KEV entry is listed.
  • Which component is affected and how an attacker would reach it.
  • Why the description says remote while the CVSS vector says Adjacent.

This article will need updating once IBM's bulletin details are confirmed by additional sources.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-114464 - GitHub Advisory Databasegithub.com
  2. CVE-2026-114464: IBM Process Mining 2.0.0 through 2.2.1 could allow a remote attacker to obtain sensitive information due to improper access control.nvd.nist.gov ·
  • IBM
  • Process Mining
  • CVE-2026-114464
  • Access control
  • CWE-284