CVE-2026-93005 (GCVE-0-2026-93005)
Vulnerability from cvelistv5 – Published: 2026-11-08 18:46 – Updated: 2026-11-08 18:46
VLAI
EPSS
VEX
Title
Multiple security vulnerabilities are addressed with IBM Process Mining Interim Fix for October 2026
Summary
IBM Process Mining 2.0.0 through 2.2.1 could allow an authenticated attacker to cause a denial of service through insufficient rate limiting of email notifications, resulting in excessive emails being sent to targeted recipients.
Severity
6.5 (Medium)
CWE
- CWE-770 - Allocation of Resources Without Limits or Throttling
Assigner
References
1 reference
| URL | Tags |
|---|---|
| https://www.ibm.com/support/pages/node/7294875 | vendor-advisorypatch |
Impacted products
1 product
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| IBM | Process Mining |
Affected:
2.0.0 , ≤ 2.2.1
(semver)
cpe:2.3:a:ibm:process_mining:2.0.0:*:*:*:*:*:*:* cpe:2.3:a:ibm:process_mining:2.2.1:*:*:*:*:*:*:* |
{
"containers": {
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:ibm:process_mining:2.0.0:*:*:*:*:*:*:*",
"cpe:2.3:a:ibm:process_mining:2.2.1:*:*:*:*:*:*:*"
],
"product": "Process Mining",
"vendor": "IBM",
"versions": [
{
"lessThanOrEqual": "2.2.1",
"status": "affected",
"version": "2.0.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eIBM Process Mining 2.0.0 through 2.2.1 could allow an authenticated attacker to cause a denial of service through insufficient rate limiting of email notifications, resulting in excessive emails being sent to targeted recipients.\u003c/p\u003e"
}
],
"value": "IBM Process Mining 2.0.0 through 2.2.1 could allow an authenticated attacker to cause a denial of service through insufficient rate limiting of email notifications, resulting in excessive emails being sent to targeted recipients."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-770",
"description": "CWE-770 Allocation of Resources Without Limits or Throttling",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-08T18:46:24.333Z",
"orgId": "9a959283-ebb5-44b6-b705-dcc2bbced522",
"shortName": "ibm"
},
"references": [
{
"tags": [
"vendor-advisory",
"patch"
],
"url": "https://www.ibm.com/support/pages/node/7294875"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cdiv\u003e\u003ctable\u003e\u003ccolgroup\u003e\u003ccol/\u003e\u003ccol/\u003e\u003ccol/\u003e\u003c/colgroup\u003e\u003ctbody\u003e\u003ctr\u003e\u003ctd\u003eProduct(s)\u003c/td\u003e\u003ctd\u003eVersion(s) number and/or range\u00a0\u003c/td\u003e\u003ctd\u003eRemediation/Fix/Instructions\u003c/td\u003e\u003c/tr\u003e\u003ctr\u003e\u003ctd\u003eIBM Process Mining OCP\u003c/td\u003e\u003ctd\u003e2.0.0 - 2.2.1\u003c/td\u003e\u003ctd\u003e\u003cp\u003eIBM strongly suggests that you address the vulnerabilities now for all affected products/versions listed above by installing 2.2.1 IF001\u003cbr/\u003e\u003cbr/\u003eUpgrade to version 2.2.1 IF001\u003cbr/\u003e\u003ca href=\"https://www.ibm.com/support/pages/readme-ibm-process-mining-221-if001\" rel=\"nofollow\"\u003ehttps://www.ibm.com/support/pages/readme-ibm-process-mining-221-if001\u003c/a\u003e\u003c/p\u003e\u003cp\u003e\u003c/p\u003e\u003c/td\u003e\u003c/tr\u003e\u003ctr\u003e\u003ctd\u003euniIBM Process Mining On-Prem\u003c/td\u003e\u003ctd\u003e2.0.0 - 2.2.1\u003c/td\u003e\u003ctd\u003e\u003cdiv\u003eIBM strongly suggests that you address the vulnerabilities now for all affected products/versions listed above by installing 2.2.1\u003cbr/\u003e\u003cbr/\u003eSteps\u003cbr/\u003e1. Go to IBM Support Portal\u003cbr/\u003eNavigate to \u003ca href=\"https://ibm.com/mysupport\" rel=\"nofollow\"\u003ehttps://ibm.com/mysupport\u003c/a\u003e and sign in with your IBMid before proceeding.\u003cbr/\u003e2. Open a case\u003c/div\u003e\u003cul\u003e\u003cli\u003eClick \"Open a case\" from the support portal.\u003c/li\u003e\u003cli\u003eSelect IBM Process Mining as the product.\u003c/li\u003e\u003cli\u003eFill in the case details, referencing the published security advisory: \u003ca href=\"https://www.ibm.com/support/pages/node/7294875\" rel=\"noopener noreferrer nofollow\"\u003ehttps://www.ibm.com/support/pages/node/7294875\u003c/a\u003e\u003c/li\u003e\u003cli\u003eRequest the delivery of IBM Process Mining 2.2.1 IF001, which addresses the documented vulnerabilities.\u003c/li\u003e\u003c/ul\u003e\u003cdiv\u003e3. Obtain the fix\u003cbr/\u003eThe interim fix will be delivered directly through your support case once it has been opened.\u003c/div\u003e\u003c/td\u003e\u003c/tr\u003e\u003c/tbody\u003e\u003c/table\u003e\u003c/div\u003e"
}
],
"value": "Product(s)Version(s) number and/or range\u00a0Remediation/Fix/InstructionsIBM Process Mining OCP2.0.0 - 2.2.1\n\nIBM strongly suggests that you address the vulnerabilities now for all affected products/versions listed above by installing 2.2.1 IF001\n\nUpgrade to version 2.2.1 IF001\n https://www.ibm.com/support/pages/readme-ibm-process-mining-221-if001 \n\n\n\n\n\nuniIBM Process Mining On-Prem2.0.0 - 2.2.1IBM strongly suggests that you address the vulnerabilities now for all affected products/versions listed above by installing 2.2.1\n\nSteps\n1. Go to IBM Support Portal\nNavigate to https://ibm.com/mysupport and sign in with your IBMid before proceeding.\n2. Open a case\n\n * Click \"Open a case\" from the support portal.\n * Select IBM Process Mining as the product.\n * Fill in the case details, referencing the published security advisory: https://www.ibm.com/support/pages/node/7294875 \n * Request the delivery of IBM Process Mining 2.2.1 IF001, which addresses the documented vulnerabilities.\n\n\n3. Obtain the fix\nThe interim fix will be delivered directly through your support case once it has been opened."
}
],
"title": "Multiple security vulnerabilities are addressed with IBM Process Mining Interim Fix for October 2026"
}
},
"cveMetadata": {
"assignerOrgId": "9a959283-ebb5-44b6-b705-dcc2bbced522",
"assignerShortName": "ibm",
"cveId": "CVE-2026-93005",
"datePublished": "2026-11-08T18:46:24.333Z",
"dateReserved": "2026-09-17T14:31:27.823Z",
"dateUpdated": "2026-11-08T18:46:24.333Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:ibm:process_mining:2.0.0:*:*:*:*:*:*:*",
"cpe:2.3:a:ibm:process_mining:2.2.1:*:*:*:*:*:*:*"
],
"product": "Process Mining",
"vendor": "IBM",
"versions": [
{
"lessThanOrEqual": "2.2.1",
"status": "affected",
"version": "2.0.0",
"versionType": "semver"
}
]
}
],
"source": "psirt@us.ibm.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "IBM Process Mining 2.0.0 through 2.2.1 could allow an authenticated attacker to cause a denial of service through insufficient rate limiting of email notifications, resulting in excessive emails being sent to targeted recipients."
}
],
"id": "CVE-2026-93005",
"lastModified": "2026-11-08T19:17:43.290",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "psirt@us.ibm.com",
"type": "Primary"
}
]
},
"published": "2026-11-08T19:17:43.177",
"references": [
{
"source": "psirt@us.ibm.com",
"url": "https://www.ibm.com/support/pages/node/7294875"
}
],
"sourceIdentifier": "psirt@us.ibm.com",
"vulnStatus": "Awaiting Analysis",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-770"
}
],
"source": "psirt@us.ibm.com",
"type": "Primary"
}
]
}
}
}
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.