CVE-2026-3366
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM InfoSphere Optim Test Data Fabrication 1.0.0, 1.0.0.1, 1.0.0.2, 1.0.2, 1.0.2.2, 1.0.2.3, 1.0.2.4, 1.0.2.5, 1.0.2.6, 1.0.2.7 could allow a remote attacker to traverse directories on the system. An attacker could send a specially crafted URL request containing "dot dot" sequences (/../) to view arbitrary files on the system
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM InfoSphere Optim Test Data Fabrication versions 1.0.0 through 1.0.2.7 contains a path traversal vulnerability. A remote unauthenticated attacker can craft HTTP requests containing '../' sequences to escape the application's intended directory and read arbitrary files on the host system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.0= 1.0.0.1= 1.0.0.2= 1.0.2= 1.0.2.2= 1.0.2.3= 1.0.2.4= 1.0.2.5= 1.0.2.6= 1.0.2.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm IBM InfoSphere Optim Test Data Fabrication is installedLocate the product installation directory. On Windows, check common paths such as C:\Program Files\IBM\Optim\Test Data Fabrication or C:\IBM\Optim\Test Data Fabrication. On Linux/Unix, check /opt/ibm/Optim/TestDataFabrication or similar. Look for executable files named optim, tdf, or containing 'Test Data Fabrication' in the product name.Affected if The product is found installed on the system regardless of version.
-
Identify installed versionCheck the product's version by examining the installed files. Look for a version file, about dialog, or product-info file within the installation directory. Common locations include <install_dir>/version.txt, <install_dir>/product.ini, or check the properties of the main executable. Alternatively, run the application with a version flag if available (such as --version or -v).Affected if The installed version matches any of these: 1.0.0, 1.0.0.1, 1.0.0.2, 1.0.2, 1.0.2.2, 1.0.2.3, 1.0.2.4, 1.0.2.5, 1.0.2.6, or 1.0.2.7.
-
Verify the web interface is accessibleIdentify if the product exposes an HTTP or HTTPS service. Check for configuration files (such as server.xml, httpd.conf, or configuration.properties) that define web service ports. Default ports for IBM Optim products are often 28080 or 8080. Attempt to access the web interface via browser or curl to the detected port.Affected if The web interface is reachable over the network on any port.
-
Check network exposureReview firewall rules, network configurations, or reverse proxy settings that expose the Optim Test Data Fabrication web service. Determine if the service is bound to localhost only (127.0.0.1) or if it listens on all interfaces (0.0.0.0). Check the server configuration file for the 'bindAddress' or 'listenAddress' setting.Affected if The service is accessible from non-localhost addresses, increasing exposure to remote attackers.
If IBM InfoSphere Optim Test Data Fabrication versions 1.0.0 through 1.0.2.7 are installed and the web interface is network-accessible, the environment is affected by this path traversal vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply IBM patches for this vulnerability. If no patch is available, implement strict input validation to reject paths containing '..' sequences, or configure the web server to restrict file access to the application root directory.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3366 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data