Cyber Resilience

CVE-2025-36327

Ibm Watsonx.Data Intelligence

Published
30 June 2026
Modified
06 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0021 11th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-36327 is a medium-severity Client-Side Enforcement of Server-Side Security (CWE-602) vulnerability in Ibm Watsonx.Data Intelligence. Its CVSS base score is 6.5 (Medium).

Operationally, ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-602

Related Threats

CVEs Like This One

CVE-2025-36328Same product: Ibm Software Hub
CVE-2025-36323Same product: Ibm Software Hub
CVE-2025-36320Same product: Ibm Software Hub
CVE-2025-36319Same product: Ibm Software Hub
CVE-2025-12530Same product: Ibm Software Hub
CVE-2025-36324Same product: Ibm Software Hub
CVE-2025-36321Same product: Ibm Software Hub
CVE-2025-36336Same product: Ibm Software Hub
CVE-2025-36333Same product: Ibm Software Hub
CVE-2024-43188Same vendor: Ibm

Affected Assets

ibm
watsonx.data intelligence
all versions

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-24 Access Control Decisions
  • SI-10 Information Input Validation
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V10.7.1
  • V2.2.2
  • V8.3.1
  • V10.4.1

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match
prevent

Directly requires the system to enforce approved authorizations on the server rather than trusting client-side logic for access decisions.

AC-24 Access Control Decisions good match
prevent

Mandates that access control decisions are made and enforced by the system itself, eliminating reliance on client-side enforcement.

SI-10 Information Input Validation partial match
prevent

Requires server-side validation of all inputs and security-relevant parameters so that client-supplied values cannot bypass intended restrictions.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent design flaws that place server security enforcement on the client.

PR.AA-05 partial match
prevents

Proper policy-based enforcement of authorizations implies server-side controls rather than client-only checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.27 Secure system architecture and engineering principles mostly match
prevents

Secure architecture principles discourage client-side trust but do not directly address this weakness.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect client-side enforcement but is not the primary mitigation.

A.8.3 Information access restriction mostly match
prevents

Information access restriction is undermined when the client is trusted to enforce it.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates server-side validation and prevents reliance on client enforcement.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for server-side enforcement of security mechanisms.

A.8.28 Secure coding partial match
prevents

Secure coding standards require server-side checks and reject client-only enforcement.

References