CVE-2025-36359: IBM DevOps Automation 1.0.1 and IBM DevOps Loop 1.0.2 does not invalidate session IDs after expiration which c

Routine

HIGH 8.1DOWNGRADEDOWNGRADE

CVE-2025-36359 is a high-severity flaw (CVSS 8.1) affecting devops automation, devops loop. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-613
Published	2026-06-30
Last modified	2026-10-06

Publisher (CNA): IBM Corporation · Vendor: ibm

Last updated 2026-10-06 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-30 21:16 UTCPublished CVE record published
2026-10-06 22:10 UTCUpdated Record last modified

ibm devops automation DOWNGRADE

Affected: 1.0.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.1

1. Check installed version

apt-cache policy devops-automation || rpm -q devops-automation || devops-automation --version

2. No fixed release: DOWNGRADE to a release before 1.0.1 (Debian / Ubuntu)

apt-cache madison devops-automation sudo apt install devops-automation=<VERSION_BEFORE_1.0.1> sudo apt-mark hold devops-automation

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list devops-automation sudo dnf downgrade devops-automation-<VERSION_BEFORE_1.0.1> sudo dnf versionlock add devops-automation

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

ibm devops loop DOWNGRADE

Affected: 1.0.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.2

1. Check installed version

apt-cache policy devops-loop || rpm -q devops-loop || devops-loop --version

2. No fixed release: DOWNGRADE to a release before 1.0.2 (Debian / Ubuntu)

apt-cache madison devops-loop sudo apt install devops-loop=<VERSION_BEFORE_1.0.2> sudo apt-mark hold devops-loop

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list devops-loop sudo dnf downgrade devops-loop-<VERSION_BEFORE_1.0.2> sudo dnf versionlock add devops-loop

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-36359?

devops automation: downgrade or apply the listed mitigation; devops loop: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-36359 being exploited?

CVE-2025-36359 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-36359 affect?

CVE-2025-36359 affects devops automation, devops loop. Severity is high (CVSS 8.1). 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.

How urgent is CVE-2025-36359?

Priority 35/100. High severity

References

← Back to latest CVEs