Token theft via forged TLS certificates
Published Oct 12, 2026 · Updated Oct 12, 2026
TLS validation in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows man-in-the-middle attackers to steal IAM tokens via forged certificates. The client-side SDK session adapter accepts a forged certificate while automatically attaching the IAM bearer Authorization header. Exploitation requires external network interception, not shared-cluster co-tenancy; the stolen token grants tenant API access to read and manipulate projects, flows, assets, and pipeline definitions.
Summary
What happened
TLS validation in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows man-in-the-middle attackers to steal IAM tokens via forged certificates. The client-side SDK session adapter accepts a forged certificate while automatically attaching the IAM bearer Authorization header. Exploitation requires external network interception, not shared-cluster co-tenancy; the stolen token grants tenant API access to read and manipulate projects, flows, assets, and pipeline definitions.
The record
- CVE
- CVE-2026-84418
- Published
- Oct 12, 2026
- Updated
- Oct 12, 2026
- Vendor
- IBM
- Product
- IBM DataStage on Cloud Pak for Data
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 12, 2026CVE publishedPublication date reported by the CVE source.
- Oct 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.4.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started