Cyber Resilience

CVE-2025-36102

Ibm Cognos Controller 11.0.0 – 11.0.1.7

Published
08 December 2025
Modified
10 December 2025
Patch / advisory
View advisory
CVSS Score v3.1 2.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0020 10th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2025-36102 is a low-severity Client-Side Enforcement of Server-Side Security (CWE-602) vulnerability in Ibm Cognos Controller. Its CVSS base score is 2.7 (Low).

Operationally, ranked at the 10th 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-3 (Access Enforcement) and SI-10 (Information Input Validation) — 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 Controller 11.1.0 through 11.1.1 and IBM Cognos Controller 11.0.0 through 11.0.1 FP6 could allow a privileged user to bypass validation, passing user input into the application as trusted data, due to client-side enforcement of server-side security.

CWE(s)
CWE-602

Related Threats

CVEs Like This One

CVE-2025-36326Same product: Ibm Cognos Controller
CVE-2025-33111Same product: Ibm Cognos Controller
CVE-2025-36015Same product: Ibm Cognos Controller
CVE-2025-33079Same product: Ibm Cognos Controller
CVE-2024-40691Same product: Ibm Cognos Controller
CVE-2024-43188Same vendor: Ibm
CVE-2024-25019Same product: Ibm Cognos Controller
CVE-2024-41778Same product: Ibm Controller
CVE-2023-23474Same product: Ibm Cognos Controller
CVE-2024-25035Same product: Ibm Cognos Controller

Affected Assets

ibm
cognos controller
11.0.0 — 11.0.1.7
ibm
controller
11.1.0 — 11.1.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • SI-10 Information Input Validation
  • AC-4 Information Flow Enforcement
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 access-control decisions on the server rather than trusting client-supplied data.

SI-10 Information Input Validation good match
prevent

Mandates server-side validation and sanitization of all input so that client-side checks cannot be bypassed.

AC-4 Information Flow Enforcement partial match
prevent

Enforces information-flow rules at trusted boundaries, preventing unvalidated client data from being treated as authoritative.

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