VulnerabilityPublished 2 Mar 2025Updated 1 Sep 2025

CVE-2025-0895: IBM Cognos Analytics Mobile · Insertion of Sensitive Information Into Debugging Code

Affects IBM Cognos Analytics MobileSource CVE Database V5

Not known to be exploited · CVSS 2.4 Low.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score

2.4Low

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

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

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

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
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: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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 2 Mar 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 Cognos Analytics Mobile	Affected =1.1	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Restrict physical access to devices running IBM Cognos Analytics Mobile, especially in high-risk environments. 2) Enforce device encryption and strong authentication mechanisms (PIN, biometrics) to prevent unauthorized access to the device and its logs. 3) Disable or restrict debug logging in production versions of the app, or ensure that debug logs do not contain sensitive information by working with IBM support or monitoring for updates. 4) Monitor and audit mobile devices for unauthorized access or suspicious activity. 5) Educate users about the risks of leaving devices unattended and the importance of reporting lost or stolen devices promptly. 6) Stay updated with IBM security advisories for patches or updates addressing this vulnerability and apply them as soon as they become available. 7) Consider mobile device management (MDM) solutions to enforce security policies and remotely wipe devices if compromised. These steps go beyond generic advice by focusing on controlling physical access, managing debug logging practices, and leveraging organizational security controls tailored to mobile device usage.

Description

IBM Cognos Analytics Mobile 1.1 for Android could allow a user with physical access to the device, to obtain sensitive information from debugging code log messages.

Impact

For European organizations using IBM Cognos Analytics Mobile 1.1 on Android devices, this vulnerability poses a risk of sensitive information leakage if devices fall into unauthorized hands. The impact is primarily on confidentiality, as attackers with physical access could extract sensitive data from debug logs. This could lead to exposure of business intelligence insights, user credentials, or other sensitive operational data, potentially facilitating further attacks or corporate espionage. Although the vulnerability requires physical access, the risk is heightened in environments where mobile devices are shared, lost, or stolen, such as field operations, remote work scenarios, or during travel. Given the widespread use of IBM Cognos Analytics in enterprise environments across Europe for data analytics and decision-making, any leakage of sensitive analytics data could undermine competitive advantage and violate data protection regulations such as GDPR if personal data is involved. However, the low CVSS score and lack of known exploits indicate that the immediate threat level is low, but organizations should not disregard the risk especially in high-security contexts.

CWE-215Insertion of Sensitive Information Into Debugging Code (opens in a new tab)
Base weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.
Implementation
Do not leave debug statements that could be executed in the source code. Ensure that all debug information is eradicated before releasing the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
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)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Sep 2025, 01:48 UTC

WeaknessesCWE-215

Technical details

References

Community reviews

Related threats