VulnerabilityPublished 9 Dec 2025

CVE-2025-36437: IBM Planning Analytics Local · Generation of Error Message Containing Sensitive Information

Affects IBM Planning Analytics LocalSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBM IBM Planning Analytics Local	Affected =2.1.0	Fixed in–

AI-suggested

Apply vendor patches promptly once available to address the root cause of the error message information leakage.
In the interim, configure IBM Planning Analytics Local to suppress detailed error messages or redirect error outputs to secure logs inaccessible to unauthorized users.
Implement network segmentation and access controls to limit exposure of the affected systems to trusted personnel and networks only.
Monitor logs for unusual access patterns or repeated error message triggers that could indicate reconnaissance attempts.
Conduct regular security assessments and penetration tests focusing on error handling and information disclosure vectors.
Educate system administrators and developers on secure error handling practices to prevent similar issues in custom configurations or integrations.
Employ web application firewalls or intrusion detection systems to detect and block attempts to exploit information disclosure vulnerabilities.
Maintain an inventory of IBM Planning Analytics Local deployments and their versions to prioritize remediation efforts effectively.

Description

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.

Impact

For European organizations, this vulnerability poses a risk primarily to confidentiality by exposing internal server architecture details that could facilitate more sophisticated attacks such as targeted exploitation or lateral movement within networks. Organizations relying on IBM Planning Analytics Local for financial planning, budgeting, or analytics may face increased risk of reconnaissance by threat actors, potentially including cybercriminals or state-sponsored groups. While the vulnerability does not directly affect system integrity or availability, the leaked information can be a stepping stone for further compromise. The impact is heightened in sectors with stringent data protection requirements, such as finance, government, and critical infrastructure, where exposure of system details can lead to regulatory penalties or operational disruptions. Since IBM Planning Analytics is widely used in enterprise environments across Europe, especially in countries with strong financial sectors, the potential for targeted attacks leveraging this vulnerability is significant if unmitigated.

CWE-209Generation of Error Message Containing Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
Implementation
Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
Implementation · Attack Surface Reduction
Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
Padding Oracle Crypto Attack (opens in a new tab)
Query System for Information (opens in a new tab)
Blind SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7253603 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Dec 2025, 23:25 UTC

WeaknessesCWE-209

Technical details

References

Community reviews

Related threats