CVE-2025-36333: Vulnerabilities found in Watson Data Intelligence
IBM watsonx.data intelligence 5.2.0, 5.2.1, 5.2.2, 5.3.0 could allow an authenticated user to perform unauthorized actions due to the improper enforcement of behavioral workflow.
Security readout for executives and security teams
Plain-English summary
IBM watsonx.data intelligence versions 5.2.0 through 5.3.0 have a workflow enforcement flaw. A logged-in user may be able to take actions they should not be allowed to perform. The impact is limited to integrity in the CVSS data, with no stated confidentiality or availability impact.
Executive priority
Handle through normal vulnerability management with moderate priority. Prioritize environments where many users have access, workflows affect sensitive business decisions, or unauthorized action integrity risks could affect compliance or operations.
Technical view
CVE-2025-36333 is a CWE-841 improper enforcement of behavioral workflow issue in IBM watsonx.data intelligence 5.2.0, 5.2.1, 5.2.2, and 5.3.0. CVSS 3.1 is 4.3: network-accessible, low complexity, low privileges required, no user interaction, unchanged scope, and low integrity impact.
Likely exposure
Exposure is limited to organizations running the affected IBM watsonx.data intelligence versions and allowing authenticated user access. The source data does not indicate unauthenticated exposure or cross-tenant impact.
Exploitation context
The sources do not report active exploitation, and this CVE is not listed as CISA KEV in the provided bundle. Exploitation requires an authenticated user and may allow unauthorized actions through improper workflow enforcement.
Researcher notes
The public description is concise and does not provide affected workflow details, exploit conditions beyond authentication, or specific remediation text in the bundle. Avoid assuming impact beyond low integrity unless IBM advisory details confirm it.
Mitigation direction
Review IBM advisory for the vendor-provided patch or remediation guidance.
Upgrade or apply fixes for affected watsonx.data intelligence versions as directed by IBM.
Restrict user privileges to the minimum required until remediation is complete.
Review workflow-related permissions and role assignments for affected deployments.
Validation and detection
Inventory watsonx.data intelligence deployments and identify versions 5.2.0, 5.2.1, 5.2.2, or 5.3.0.
Confirm whether IBM advisory remediation has been applied.
Review audit logs for authenticated users performing unexpected workflow actions.
Verify role-based access controls and workflow authorization behavior after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-841: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-841 · source CWE mapping
Improper Enforcement of Behavioral Workflow
Improper Enforcement of Behavioral Workflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.