VulnerabilityPublished 17 Mar 2026

CVE-2026-1267: IBM Planning Analytics Local · Information Exposure

Affects IBM Planning Analytics LocalSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% 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:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: 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: 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 17 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 Local	Affected >=2.1.0 <=2.1.17	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:planning_analytics_local:2.1.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:planning_analytics_local:2.1.17:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-1267, organizations should first apply any patches or updates released by IBM addressing this vulnerability once available. In the absence of immediate patches, administrators should enforce strict network segmentation and limit access to IBM Planning Analytics Local instances to trusted internal networks only. Implement robust role-based access controls (RBAC) and audit existing user privileges to ensure that only authorized personnel have access to sensitive data and administrative functions. Regularly review and harden authentication mechanisms, including enforcing strong password policies and multi-factor authentication where supported. Monitor logs and access patterns for unusual activity that may indicate exploitation attempts. Additionally, consider deploying web application firewalls (WAFs) or intrusion detection/prevention systems (IDS/IPS) to detect and block suspicious access attempts. Conduct security awareness training for administrators to recognize and respond to potential exploitation signs. Finally, maintain up-to-date backups and incident response plans tailored to potential data exposure scenarios.

Description

CVE-2026-1267 is a medium severity vulnerability in IBM Planning Analytics Local versions 2.1.0 through 2.1.17. It allows unauthorized actors with limited privileges to access sensitive application data and administrative functions due to insufficient access controls. The vulnerability does not require user interaction and can be exploited remotely over the network. While it does not impact system integrity or availability, the confidentiality breach could expose critical business data. No known exploits are currently reported in the wild. Organizations using affected versions should prioritize patching or implementing compensating controls to restrict unauthorized access.

Impact

The primary impact of CVE-2026-1267 is the unauthorized disclosure of sensitive business and administrative data within IBM Planning Analytics Local environments. This can lead to significant confidentiality breaches, exposing financial plans, operational data, or administrative configurations to unauthorized parties. Such exposure can undermine competitive advantage, violate data privacy regulations, and damage organizational reputation. Although the vulnerability does not directly affect system integrity or availability, the unauthorized access to administrative functionalities could potentially be leveraged in chained attacks to escalate privileges or manipulate configurations indirectly. Organizations relying heavily on IBM Planning Analytics Local for critical business processes may face operational risks if sensitive data is leaked or misused. The absence of known exploits reduces immediate risk, but the medium severity score and ease of remote exploitation warrant prompt attention. The impact is heightened in sectors with stringent compliance requirements such as finance, healthcare, and government, where data confidentiality is paramount.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
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)
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)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

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

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats