VulnerabilityPublished 17 Nov 2025

CVE-2025-36299: IBM Planning Analytics Local · CWE-540

Affects IBM Planning Analytics LocalSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 10:12 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 13% 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 17 Nov 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

To mitigate CVE-2025-36299, European organizations should: 1) Immediately audit all instances of IBM Planning Analytics Local to identify versions 2.1.0 through 2.1.14 in use. 2) Restrict access to source code repositories and configuration files to only essential personnel, enforcing strict role-based access controls. 3) Conduct thorough code reviews to identify and remove any sensitive information stored in source code, replacing them with secure vault or environment variable mechanisms. 4) Monitor internal networks for unusual access patterns that could indicate attempts to access source code or sensitive files. 5) Engage with IBM support to obtain and apply patches or updates as soon as they become available. 6) Implement network segmentation to isolate analytics environments from broader corporate networks. 7) Educate development and operations teams about secure coding practices to prevent embedding sensitive data in source code in the future. 8) Use data loss prevention (DLP) tools to detect sensitive information in code repositories and prevent unauthorized exfiltration.

Description

IBM Planning Analytics Local 2.1.0 through 2.1.14 stores sensitive information in source code could be used in further attacks against the system.

Impact

For European organizations, the impact of CVE-2025-36299 primarily involves the potential leakage of sensitive information embedded in source code, which could include credentials or configuration secrets. This leakage could enable attackers to escalate privileges, move laterally within networks, or access confidential business data, especially in sectors relying heavily on IBM Planning Analytics Local for financial and operational planning. While the vulnerability does not directly affect system integrity or availability, the confidentiality breach could lead to regulatory compliance issues under GDPR, reputational damage, and financial losses. Organizations in finance, manufacturing, and large enterprises using IBM Planning Analytics Local are at heightened risk. The medium severity score reflects that exploitation requires some privileges, limiting the attack surface but not eliminating risk. The absence of known exploits suggests a window for proactive defense, but also underscores the need for vigilance as threat actors may develop exploits targeting this vulnerability.

CWE-540Inclusion of Sensitive Information in Source Code (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.
Architecture and Design · System Configuration
Recommendations include removing this script from the web server and moving it to a location not accessible from the Internet.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (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)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Nov 2025, 20:24 UTC

WeaknessesCWE-540

Technical details

References

Community reviews

Related threats