CVE-2025-36437

Info Disclosure in Ibm Planning Analytics Local 2.1.0 – 2.1.16

Info Disclosure

Published

09 December 2025

Modified

14 January 2026

Patch / advisory

View advisory

CVSS Score v3.1 4.3

Click a component to see what it means

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS Score 0.0019 9th percentile

Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-36437 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Ibm Planning Analytics Local. Its CVSS base score is 4.3 (Medium).

Operationally, ranked at the 9th 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 SI-11 (Error Handling) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2025-202332

Vulnerability Data

IBM Planning Analytics Local 2.1.0 - 2.1.15 could disclose sensitive information about server architecture that could aid in further attacks against the system.

CWE(s): CWE-209

Related Threats

CVEs Like This One

CVE-2025-33005Same product: Ibm Planning Analytics Local

CVE-2025-36132Same product: Ibm Planning Analytics Local

CVE-2025-33004Same product: Ibm Planning Analytics Local

CVE-2024-31889Same product: Ibm Planning Analytics Local

CVE-2023-28520Same product: Ibm Planning Analytics Local

CVE-2025-2896Same product: Ibm Planning Analytics Local

CVE-2025-25044Same product: Ibm Planning Analytics Local

CVE-2024-31907Same product: Ibm Planning Analytics Local

CVE-2025-36262Same product: Ibm Planning Analytics Local

CVE-2024-31908Same product: Ibm Planning Analytics Local

Affected Assets

ibm

planning analytics local

2.1.0 — 2.1.16

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

SI-11 Error Handling
AC-4 Information Flow Enforcement

Detect

Catch it (NIST detect / respond)

AU-13 Monitoring for Information Disclosure

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

V16.5.1

Mitigating Controls (NIST 800-53 r5) AI

SI-11 Error Handling good match

prevent

Directly requires error messages to avoid revealing sensitive system details (server architecture) that could be exploited, matching CWE-209 root cause.

AU-13 Monitoring for Information Disclosure partial match

detect

Monitors specifically for unauthorized information disclosure events that would expose internal architecture details.

AC-4 Information Flow Enforcement partial match

prevent

Enforces information flow policies to block unauthorized exposure of system architecture data via error paths or responses.

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 require sanitized error handling to prevent sensitive data disclosure.

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.28 Secure coding mostly match

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

A.8.29 Security testing in development and acceptance mostly match

detects

Security testing can detect error messages that leak sensitive information.

A.8.15 Logging partial match

degrades

Logging policy can require suppression of sensitive data in error messages.

A.8.25 Secure development life cycle partial match

prevents

Secure SDLC mandates error-handling rules that avoid leaking sensitive information.