Skip to main content

IBM DevOps Automation CVE-2025-36359

| EUVDEUVD-2025-210374 MEDIUM
Insufficient Session Expiration (CWE-613)
2026-06-30 ibm GHSA-85r2-j732-h557
6.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege user
  2. Delivery
    Obtain victim's expired session ID
  3. Exploit
    Replay stale session token
  4. Execution
    Server accepts non-invalidated session
  5. Impact
    Impersonate victim and access their data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V7 - Session Management Session expiration enforcement
Exploitation Conditions

Exploitation requires that the attacker already holds valid authentication to the platform (PR:L) and obtains a victim's session ID that has reached its intended expiration but is still accepted by the server. The core flaw is that expired session IDs are not invalidated, so the limiting factor is access to such a token (via shared or logged-out sessions, captured identifiers, or reuse) rather than any special product feature flag or non-default setting. Limiting factors: the attacker must be authenticated, must acquire the target's session identifier, and the impact is confined to confidentiality and integrity (A:N) with no availability or denial-of-service angle.

Impact

The vendor CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, base 8.1) indicates network-reachable, low-complexity exploitation by an already-authenticated low-privilege user, with high confidentiality and integrity impact but no availability impact - consistent with account impersonation rather than service disruption. No EPSS score, KEV listing, or SSVC decision data was provided, and no public exploit was identified, so practical risk is moderated by the PR:L requirement: the attacker must already hold valid credentials and must also obtain another user's (expired) session token. There is no signal of active or widespread exploitation, so this is a meaningful but not emergency patch priority. Note the high base score is driven by the impersonation impact, not by the ease of obtaining the victim's token - a step the vector does not separately capture.

Exploit ScenarioDerived

An authenticated low-privilege user of IBM DevOps Automation captures or retains another user's session identifier - for example one that should have been invalidated after timeout - and replays it against the application. Because the server still accepts the expired ID, the attacker is authenticated as the victim and performs actions under that identity, reaching pipelines and data they should not control. No public proof-of-concept exists at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 30, 2026

Session hijacking in IBM DevOps Automation 1.0.1 and IBM DevOps Loop 1.0.2 allows an authenticated user to impersonate another user because session IDs are not invalidated after they expire (CWE-613). An attacker who obtains or reuses a stale session identifier can act with the victim's identity, producing high confidentiality and integrity impact. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.

RemediationAI

Apply the vendor patch referenced in IBM's advisory at https://www.ibm.com/support/pages/node/7277970 (Patch available per vendor advisory; an exact fixed version is not stated in the provided data, so confirm the target release on that page before deploying). Until patched, reduce exposure by shortening server-side session lifetimes and forcing re-authentication, ensuring sessions are destroyed server-side (not merely expired client-side) on logout and timeout, and where supported rotating or invalidating session IDs on context or privilege change; the trade-off is more frequent logins for users and possible disruption to long-running automation sessions. Restricting network access to the management interfaces to trusted users and networks further limits who can attempt to replay stale tokens.

Affected VersionsENISA

DevOps Automation 1.0.1
DevOps Loop 1.0.2

Affected Packages

euvd devops_automation no fix
euvd devops_loop no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

IBM DevOps Automation and IBM DevOps Loop are enterprise CI/CD and release-orchestration platforms (CPEs cpe:2.3:a:ibm:devops_automation and cpe:2.3:a:ibm:devops_loop). The root cause is CWE-613 (Insufficient Session Expiration): the application continues to honor session identifiers after their intended expiration window rather than invalidating them server-side. Because the session token is the authentication anchor for web requests, a session ID that stays valid past expiration becomes a reusable credential, decoupling authentication from any time limit and enabling impersonation if the token is captured, replayed, or otherwise reused.

Severity by source

Vendor (ibm) PRIMARY HIGH
NVD 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 8.1 HIGH

Network-facing app exploited by an already-authenticated user (PR:L); reuse of a non-invalidated session yields full impersonation (C:H/I:H) with no availability impact (A:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

2
Severity Changed
Jul 06, 2026 - 16:37 NVD
HIGH MEDIUM
CVSS changed
Jul 06, 2026 - 16:37 NVD
8.1 (HIGH) 6.5 (MEDIUM)

DescriptionNVD

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.

Executive ViewAI

Why It Matters

IBM DevOps Automation 1.0.1 and IBM DevOps Loop 1.0.2 contain a critical session hijacking vulnerability enabling attackers to assume legitimate user identities and operate DevOps infrastructure without re-authentication. Although no public exploit has been identified at time of analysis, this represents immediate and high-impact risk to organizations relying on these tools for production systems. Urgent vendor patching is required.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Low
niche enterprise DevOps tools at very early 1.0.x releases
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy