dbcve.org
Watsonx.data IntelligenceApplication · Ibm

CVE-2025-36327

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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 · unedited
IBM watsonx.data intelligence 5.2.0, 5.2.1, 5.2.2, 5.3.0 could allow an authenticated user to bypass security controls and perform unauthorized actions due to client-side enforcement of sever-side security.

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 · moderate confidence

IBM watsonx.data intelligence versions 5.2.0 through 5.3.0 contains a client-side enforcement vulnerability where the server relies on client-side controls (e.g., JavaScript validation, hidden fields, UI restrictions) rather than properly validating authorization and enforcing security server-side. An authenticated user can manipulate these client-side controls to bypass security restrictions and perform unauthorized actions.

MitigationApply IBM's security patch for this vulnerability (contact IBM support for fix availability) and ensure all security controls are enforced server-side rather than relying on client-side validation.

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
Watsonx.data IntelligenceApplication
Affected:all versions

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed watsonx.data intelligence version
    Use the IBM product version lookup method (typically via the product UI under About, or via command line tools such as 'lsnode -version' or the IBM Cloud Pak for Data CLI: 'cpd-cli manage --version'), or check the installation manifest/package metadata
    Affected if The installed version falls between 5.2.0 and 5.3.0 inclusive, or is unknown/unlisted and client-side controls are in use
  2. Review application for client-side authorization controls
    Inspect web application traffic using browser developer tools or a proxy (Burp Suite, ZAP) to observe if JavaScript, hidden form fields, or UI elements are being used to enforce security decisions rather than server-side validation
    Affected if Authorization checks are performed client-side (JavaScript validation, hidden fields, disabled UI elements) instead of server-side validation for sensitive operations
  3. Test for authorization bypass via client-side manipulation
    Intercept and modify HTTP requests to bypass disabled UI elements or client-side validation checks. Attempt to access resources or perform actions that are restricted by client-side controls but may not have server-side enforcement
    Affected if Requests with manipulated client-side parameters (hidden fields, disabled buttons, modified JavaScript values) succeed when they should be rejected server-side
  4. Verify server-side authorization enforcement
    Review application logs or use authenticated accounts with different privilege levels to confirm that the server independently validates authorization for each request, not relying on client-side state or validation
    Affected if The server does not perform independent authorization validation and accepts client-provided security decisions

A user is affected if watsonx.data intelligence version 5.2.0 through 5.3.0 is installed AND the application relies on client-side controls (JavaScript, hidden fields, UI restrictions) for authorization rather than enforcing security server-side.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM's security patch for this vulnerability (contact IBM support for fix availability) and ensure all security controls are enforced server-side rather than relying on client-side validation.

Fix this in Watsonx.data Intelligence Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36327 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36327 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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