CVE-2025-33005: IBM Planning Analytics Local · Insufficient Session Expiration
Affects IBM Planning Analytics LocalSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% 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:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 1 Jun 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM Planning Analytics Local | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Immediately review and enforce session management policies within IBM Planning Analytics Local, including manual session invalidation where possible. 2) Restrict access to the IBM Planning Analytics Local environment to trusted networks and users, employing network segmentation and zero-trust principles. 3) Monitor session activity logs for anomalies such as multiple concurrent sessions from the same user or sessions persisting beyond logout events. 4) Apply strict authentication controls, including multi-factor authentication (MFA), to reduce the risk of unauthorized authenticated access. 5) Regularly update and patch IBM Planning Analytics Local once IBM releases a fix for this vulnerability. 6) Educate users about secure logout practices and the risks of session reuse. 7) Consider implementing additional session timeout controls at the web server or application gateway level to forcibly expire sessions after logout or inactivity. 8) Conduct periodic security assessments and penetration testing focused on session management to identify and remediate similar issues proactively.
Description
IBM Planning Analytics Local 2.0 and 2.1 does not invalidate session after a logout which could allow an authenticated user to impersonate another user on the system.