VulnerabilityPublished 3 Mar 2026Updated 4 Mar 2026

CVE-2026-1265: IBM InfoSphere Information Server · Sensitive Data in Logs

Affects IBM InfoSphere Information ServerSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium.

Data as of 29 Oct 2026, 19:04 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 12% 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 3 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 29 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
IBMInfoSphere Information Server	Affected >=11.7.0.0 <=11.7.1.6	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:infosphere_information_server:11.7.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:infosphere_information_server:11.7.1.6:*:*:*:*:*:*:*

AI-suggested

Until an official patch is released, organizations should implement the following mitigations: 1) Audit and restrict access permissions to log files to the minimum necessary users and processes, ensuring that only trusted administrators can view logs. 2) Review and modify logging configurations to exclude sensitive information from being logged, such as credentials, personal data, or proprietary details. 3) Employ log management solutions that support encryption and access controls to protect log data at rest and in transit. 4) Monitor logs for unusual access patterns that could indicate attempts to exploit this vulnerability. 5) Educate privileged users about the sensitivity of log data and enforce strict operational security practices. 6) Plan for timely deployment of patches or updates from IBM once available. 7) Consider implementing data masking or redaction techniques within the application or logging framework to prevent sensitive data from being recorded.

Description

IBM InfoSphere Information Server 11.7.0.0 through 11.7.1.6 is vulnerable to writing of sensitive Information in a log file.

Impact

The primary impact of CVE-2026-1265 is the potential unauthorized disclosure of sensitive information through log files. This can lead to exposure of credentials, personally identifiable information (PII), or proprietary business data, which attackers could leverage for further compromise, social engineering, or regulatory non-compliance. Although the vulnerability does not affect system integrity or availability, the confidentiality breach can undermine trust and lead to financial or reputational damage. Organizations in regulated industries such as finance, healthcare, and government are particularly vulnerable due to the sensitivity of data processed by IBM InfoSphere. The requirement for low privileges to exploit means insider threats or compromised accounts could easily access sensitive logs. The absence of known exploits reduces immediate risk, but the vulnerability remains a significant concern for data protection and compliance.

Summary

CVE-2026-1265 identifies a vulnerability in IBM InfoSphere Information Server versions 11.7.0.0 through 11.7.1.6, where sensitive information is inadvertently written into log files. This issue is categorized under CWE-532, which involves the insertion of sensitive data into log files, potentially exposing confidential information such as credentials, personal data, or proprietary business information. The vulnerability arises due to insufficient sanitization or filtering of sensitive data before logging, allowing sensitive content to be recorded in logs accessible to users or processes with access rights to these files. The CVSS v3.1 base score is 4.3 (medium), reflecting that the vulnerability can be exploited remotely over the network (AV:N) with low attack complexity (AC:L) but requires privileges (PR:L), and no user interaction (UI:N) is needed. The impact is limited to confidentiality (C:L), with no effect on integrity or availability. No patches have been published at the time of reporting, and no known exploits are in the wild. The vulnerability affects a widely used enterprise data integration and governance platform, which is often deployed in environments handling sensitive business and personal data. Attackers with limited privileges could access logs containing sensitive information, increasing the risk of data leakage or aiding further attacks.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 11 Mar 2026, 20:12 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats