CVE-2026-17466 (GCVE-0-2026-17466)
Vulnerability from cvelistv5 – Published: 2026-11-08 17:51 – Updated: 2026-11-08 17:51- CWE-22 - Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
| URL | Tags |
|---|---|
| https://www.ibm.com/support/pages/node/7289719 | vendor-advisorypatch |
{
"containers": {
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:ibm:optim:1.0.0:*:*:*:*:*:*:*",
"cpe:2.3:a:ibm:optim:1.1.0:*:*:*:*:*:*:*",
"cpe:2.3:a:ibm:optim:1.2.0:*:*:*:*:*:*:*"
],
"product": "Optim",
"vendor": "IBM",
"versions": [
{
"status": "affected",
"version": "1.0.0"
},
{
"status": "affected",
"version": "1.1.0"
},
{
"status": "affected",
"version": "1.2.0"
}
]
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eIBM Optim 1.0.0, 1.1.0, and 1.2.0 could allow a remote authenticated attacker to obtain sensitive information due to path traversal.\u003c/p\u003e"
}
],
"value": "IBM Optim 1.0.0, 1.1.0, and 1.2.0 could allow a remote authenticated attacker to obtain sensitive information due to path traversal."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-22",
"description": "CWE-22 Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-08T17:51:39.935Z",
"orgId": "9a959283-ebb5-44b6-b705-dcc2bbced522",
"shortName": "ibm"
},
"references": [
{
"tags": [
"vendor-advisory",
"patch"
],
"url": "https://www.ibm.com/support/pages/node/7289719"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eIBM strongly recommends addressing the vulnerability now.\u003c/p\u003e\u003cp\u003eMove to IBM Optim Test Data Management 2.0.0 IBM Optim Test Data Management 2.0.0 resolves all three vulnerabilities.\u003c/p\u003e\u003cp\u003eFile Path Traversal (ID: 218782) \u2014 The application now validates that file paths requested by users stay within the permitted directory. Any request attempting to access files outside that boundary is rejected.\u003c/p\u003e\u003cp\u003eNo Rate Limit (ID: 218776) \u2014 The application now enforces request rate limits per user on protected endpoints and per IP address on login endpoints. Requests that exceed the limit are blocked until the rate drops back within bounds.\u003c/p\u003e\u003cp\u003eWeak Password Policy (ID: 218648) \u2014 Default accounts and passwords have been removed. A unique administrator password is now generated automatically during installation.\u003cbr/\u003e\u003cbr/\u003e\u003cbr/\u003eAvailable from \u003ca href=\"https://www.ibm.com/software/passportadvantage/pao-customer\" rel=\"nofollow\"\u003ehttps://www.ibm.com/software/passportadvantage/pao-customer\u003c/a\u003e\u003c/p\u003e"
}
],
"value": "IBM strongly recommends addressing the vulnerability now.\n\n\n\nMove to IBM Optim Test Data Management 2.0.0 IBM Optim Test Data Management 2.0.0 resolves all three vulnerabilities.\n\n\n\nFile Path Traversal (ID: 218782) \u2014 The application now validates that file paths requested by users stay within the permitted directory. Any request attempting to access files outside that boundary is rejected.\n\n\n\nNo Rate Limit (ID: 218776) \u2014 The application now enforces request rate limits per user on protected endpoints and per IP address on login endpoints. Requests that exceed the limit are blocked until the rate drops back within bounds.\n\n\n\nWeak Password Policy (ID: 218648) \u2014 Default accounts and passwords have been removed. A unique administrator password is now generated automatically during installation.\n\n\nAvailable from https://www.ibm.com/software/passportadvantage/pao-customer"
}
],
"title": "IBM Optim Test Data Management 1.0.0, 1.1.0, and 1.2.0 impacted by Path Traversal, Rate Limiting, and Weak Password Policy vulnerabilities"
}
},
"cveMetadata": {
"assignerOrgId": "9a959283-ebb5-44b6-b705-dcc2bbced522",
"assignerShortName": "ibm",
"cveId": "CVE-2026-17466",
"datePublished": "2026-11-08T17:51:39.935Z",
"dateReserved": "2026-07-25T20:16:15.375Z",
"dateUpdated": "2026-11-08T17:51:39.935Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:ibm:optim:1.0.0:*:*:*:*:*:*:*",
"cpe:2.3:a:ibm:optim:1.1.0:*:*:*:*:*:*:*",
"cpe:2.3:a:ibm:optim:1.2.0:*:*:*:*:*:*:*"
],
"product": "Optim",
"vendor": "IBM",
"versions": [
{
"status": "affected",
"version": "1.0.0"
},
{
"status": "affected",
"version": "1.1.0"
},
{
"status": "affected",
"version": "1.2.0"
}
]
}
],
"source": "psirt@us.ibm.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "IBM Optim 1.0.0, 1.1.0, and 1.2.0 could allow a remote authenticated attacker to obtain sensitive information due to path traversal."
}
],
"id": "CVE-2026-17466",
"lastModified": "2026-11-08T18:17:03.410",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L",
"version": "3.1"
},
"exploitabilityScore": 3.1,
"impactScore": 5.3,
"source": "psirt@us.ibm.com",
"type": "Primary"
}
]
},
"published": "2026-11-08T18:17:03.303",
"references": [
{
"source": "psirt@us.ibm.com",
"url": "https://www.ibm.com/support/pages/node/7289719"
}
],
"sourceIdentifier": "psirt@us.ibm.com",
"vulnStatus": "Awaiting Analysis",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-22"
}
],
"source": "psirt@us.ibm.com",
"type": "Primary"
}
]
}
}
}
}
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.
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…
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.
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.