CVE-2025-36359: IBM DevOps Automation · Insufficient Session Expiration
Affects IBM DevOps AutomationSource CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 13 Nov 2026, 23:53 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% 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:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Jun 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 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMDevOps Automation | Affected
| Fixed in– |
| IBMDevOps Loop | Affected
| Fixed in– |
CPE configurations (2)
cpe:2.3:a:ibm:devops_automation:1.0.1:*:*:*:*:*:*:*cpe:2.3:a:ibm:devops_loop:1.0.2:*:*:*:*:*:*:*
AI-suggested
Until an official fix is available, restrict access to trusted users only and monitor for suspicious session reuse. Avoid relying on session IDs alone for authentication and consider implementing additional session management controls.
Description
IBM DevOps Automation 1.0.1 and IBM DevOps Loop 1.0.2 does not invalidate session IDs after expiration which could allow an authenticated user to impersonate another user on the system.