VulnerabilityPublished 10 Mar 2026

CVE-2025-36105: IBM Planning Analytics Advanced Certified Containers · Cleartext Storage of Sensitive Information in an Environment Variable

Affects IBM Planning Analytics Advanced Certified ContainersSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.4 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

4.4Medium

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

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
IBMPlanning Analytics Advanced Certified Containers	Affected >=3.1.0 <=3.1.4	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:planning_analytics_advanced_certified_containers:3.1.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:planning_analytics_advanced_certified_containers:3.1.4:*:*:*:*:*:*:*

AI-suggested

Restrict local privileged access strictly to trusted administrators and monitor for unauthorized privilege escalations.
Implement robust access controls and auditing on systems running IBM Planning Analytics containers to detect suspicious access to environment variables.
Avoid storing sensitive information in environment variables; use secure secret management solutions or encrypted storage mechanisms instead.
Apply vendor patches or updates promptly once available to address this vulnerability directly.
Employ container security best practices, including minimizing container privileges and isolating workloads.
Conduct regular security reviews and penetration testing focusing on container environments to identify and remediate similar issues.
Use runtime security tools that can detect anomalous access to environment variables or sensitive data within containers.
Educate administrators and users about the risks of local privilege misuse and enforce strict operational security policies.

Description

IBM Planning Analytics Advanced Certified Containers 3.1.0 through 3.1.4 could allow a local privileged user to obtain sensitive information from environment variables.

Impact

The primary impact of this vulnerability is the potential unauthorized disclosure of sensitive information stored in environment variables. If a local privileged user is compromised or malicious, they could extract credentials, tokens, or other confidential data, which could then be used to escalate privileges, move laterally within the network, or access other sensitive systems. While the vulnerability does not directly affect system integrity or availability, the confidentiality breach could lead to broader security incidents, including data breaches or compliance violations. Organizations relying on IBM Planning Analytics Advanced Certified Containers in environments with multiple users or shared infrastructure are at higher risk. The requirement for local privileged access limits remote exploitation but does not eliminate risk from insider threats or attackers who have already gained elevated access.

CWE-526Cleartext Storage of Sensitive Information in an Environment Variable (opens in a new tab)
Variant weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product uses an environment variable to store unencrypted sensitive information.
Architecture and Design
Encrypt information stored in the environment variable to protect it from being exposed to an unauthorized user. If encryption is not feasible or is considered too expensive for the business use of the application, then consider using a properly protected configuration file instead of an environment variable.
Implementation
If the environment variable is not necessary for the desired behavior, then remove it entirely, or clear it to an empty value.
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 10 Mar 2026, 01:33 UTC

WeaknessesCWE-526

Technical details

References

Community reviews

Related threats