CVE-2026-1267
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM Planning Analytics Local 2.1.0 through 2.1.17 could allow an unauthorized access to sensitive application data and administrative functionalities due to lack of proper access controls.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM Planning Analytics Local versions 2.1.0 through 2.1.17 contains improper access control mechanisms that permit unauthenticated or unauthorized users to access sensitive application data and administrative functions, potentially leading to data exposure or privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.1.0, < 2.1.18CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if IBM Planning Analytics Local is installedLocate the IBM Planning Analytics Local installation directory or check installed programs on the system. Common locations include C:\Program Files\IBM\PA or /opt/ibm/pa. On Windows, use Control Panel > Programs and Features to find the product.Affected if IBM Planning Analytics Local is present on the system
-
Determine the installed version numberCheck the application's About section, version information in the installation directory, or examine the product documentation for version details. The version is typically displayed in the TM1/Planning Analytics web interface or can be found in version metadata files within the installation folder.Affected if The version cannot be determined or is not visible
-
Compare your version against the affected rangeIf you have identified the version number, compare it to the affected range: 2.1.0 through 2.1.17 inclusive. Any version >= 2.1.0 and < 2.1.18 is affected by this vulnerability.Affected if The installed version is 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7, 2.1.8, 2.1.9, 2.1.10, 2.1.11, 2.1.12, 2.1.13, 2.1.14, 2.1.15, 2.1.16, or 2.1.17
If IBM Planning Analytics Local version 2.1.0 through 2.1.17 is installed, the environment is affected by CVE-2026-1267 and the improper access control vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.1.18
Apply the vendor-supplied patch or upgrade to a version beyond 2.1.17. If immediate patching is not possible, implement compensating controls such as network segmentation and strict firewall rules to limit access to the application.
2.1.18
- Download IBM Planning Analytics Local version 2.1.18 from IBM Fix Central or your authorized IBM distribution channel
- Review IBM Planning Analytics Local upgrade documentation before proceeding
- Back up all existing Planning Analytics Local data and configurations
- Stop all Planning Analytics Local services
- Install version 2.1.18 following IBM's standard upgrade procedures
- Restart Planning Analytics Local services
- Verify the installation was successful and the access control vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1267 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1267 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data