CVE-2023-27291 is a medium severity (CVSS 4.5) flaw in IBM Watson CP4D Data Stores, a service in IBM Cloud Pak for Data. It does not encrypt sensitive information before storage or transmission. Versions 4.6.0 to 4.6.3 are affected, so upgrade to 4.6.4 or later.
What's affected
The record and IBM Security Bulletin 6965458 agree. Affected versions are Watson CloudPak for Data Data Stores 4.6.0, 4.6.1, 4.6.2 and 4.6.3. IBM's remediation is to install CP4D services containing Watson CloudPak for Data Data Stores at version 4.6.4 or later, and it links the upgrade documentation for the 4.6.x line. IBM lists no workarounds or mitigations.
The score matches as well: IBM shows a base score of 4.5 with a network vector, low complexity, high privileges required, user interaction required, and a high confidentiality impact only. The X-Force ID is 248740. The bulletin was first published on 21 March 2023. There is no conflict between the sources.
The weakness is CWE-319, cleartext transmission of sensitive information. The bulletin text covers both storage and transmission, so treat both as in scope until your own review shows otherwise.
How to check if you're exposed
Cloud Pak for Data runs on OpenShift, so version checks use the cluster. Use the product's own tooling to list installed services and their versions. IBM's documentation for the 4.6.x line covers this, and the bulletin links it. I am not offering a specific command because I did not confirm one in the sources.
Compare the reported Data Stores version with 4.6.0 through 4.6.3. Anything in that range needs the upgrade. If your platform team manages upgrades, ask for the current service version in writing, as a mismatch between the platform version and the service version is common.
To see which of your own applications pull in affected components, run the free in-browser dependency scan at gold.safeguard.sh/scan.
What to do now
- Ask the platform owner for the installed Watson CP4D Data Stores version.
- Upgrade the service to 4.6.4 or later using IBM upgrade documentation.
- Review which data the service stores or moves, and who can read it.
- Check network paths between clients and the service for plain text traffic you control.
- Record the upgrade and close the finding with the version evidence.
Why it matters
Not encrypting sensitive data is a design weakness, not a bug in one function. If data is stored or sent in plain form, anyone who can read the disk or watch the connection can read the data. The score is low because the vector needs high privileges and user interaction, and because only confidentiality is affected.
Data platforms hold information from many teams, so a low score can still matter. Encryption in transit and at rest is often a compliance expectation. The record does not flag the CVE in CISA KEV, and IBM does not describe exploitation.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is there a workaround?
IBM lists no workarounds or mitigations. Upgrade to 4.6.4 or later.
Do the record and IBM agree?
Yes, on versions, score and fix.
Sources
- IBM Security Bulletin 6965458
- IBM X-Force entry 248740 (referenced in the record; page needs JavaScript)
- Gold entry
Last reviewed: 19 October 2026.