Unauthenticated access via default manufacturing passwords
Published May 26, 2026 · Updated May 26, 2026
Default-credential handling in IBM Cloud Pak for Data System Cyclops 11.3.0.2 through Interim Fix 002 allows remote attackers to bypass authentication. The installation credential workflow uses manufacturing-set default passwords rather than unique per-installation values. No privileges or user interaction are required; successful use grants the access assigned to the default-password account, whose permissions IBM does not specify.
Summary
What happened
Default-credential handling in IBM Cloud Pak for Data System Cyclops 11.3.0.2 through Interim Fix 002 allows remote attackers to bypass authentication. The installation credential workflow uses manufacturing-set default passwords rather than unique per-installation values. No privileges or user interaction are required; successful use grants the access assigned to the default-password account, whose permissions IBM does not specify.
The record
- CVE
- CVE-2025-36221
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- OpenBMC Project
- Product
- IBM Cloud Pak for Data System Cyclops
- Classifications
- CWE-1392, T1078.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 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=11.3.0.2 <=Interim Fix 002
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.
Weakness, pattern, technique
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo