CVE-2025-36359

MEDIUMNVD 6.58.1▲
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-30. NVD baseline CVSS 6.5; sources differ by 1.6.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
8.1(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
8.7%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 6, 2026

Advisory Details (1)

Auto-updated Jul 2, 2026
No patch confirmed yet.
generic

Security Bulletin: IBM DevOps Loop is susceptible to an Insufficient Session Expiration vulnerability. [CVE-2025-36359]

https://www.ibm.com/support/pages/node/7277970

Vendor Advisories for CVE-2025-36359(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 69× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:54 UTCEG score recompute
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:07 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 02:28 UTCEPSS rescore
  9. 2026-07-19 02:28 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-17 06:02 UTCGHSA enrichment
  13. 2026-07-16 18:34 UTCGHSA enrichment
  14. 2026-07-16 17:02 UTCEPSS rescore
  15. 2026-07-16 06:48 UTCGHSA enrichment
  16. 2026-07-15 19:12 UTCGHSA enrichment
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 07:40 UTCGHSA enrichment
  20. 2026-07-15 01:59 UTCEPSS rescore
  21. 2026-07-15 01:59 UTCEPSS rescore
  22. 2026-07-14 20:08 UTCGHSA enrichment
  23. 2026-07-14 08:39 UTCGHSA enrichment
  24. 2026-07-13 22:29 UTCEPSS rescore
  25. 2026-07-13 22:29 UTCEPSS rescore
Show 44 more
  1. 2026-07-13 21:09 UTCGHSA enrichment
  2. 2026-07-13 09:40 UTCGHSA enrichment
  3. 2026-07-13 06:12 UTCEPSS rescore
  4. 2026-07-12 22:12 UTCGHSA enrichment
  5. 2026-07-12 10:43 UTCGHSA enrichment
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 23:15 UTCGHSA enrichment
  8. 2026-07-11 11:46 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 00:17 UTCGHSA enrichment
  12. 2026-07-10 12:47 UTCGHSA enrichment
  13. 2026-07-10 01:15 UTCGHSA enrichment
  14. 2026-07-09 19:09 UTCEPSS rescore
  15. 2026-07-09 19:09 UTCEPSS rescore
  16. 2026-07-09 13:45 UTCGHSA enrichment
  17. 2026-07-09 02:17 UTCGHSA enrichment
  18. 2026-07-08 14:43 UTCGHSA enrichment
  19. 2026-07-08 03:13 UTCGHSA enrichment
  20. 2026-07-07 15:38 UTCGHSA enrichment
  21. 2026-07-07 13:45 UTCEPSS rescore
  22. 2026-07-07 03:56 UTCGHSA enrichment
  23. 2026-07-06 16:27 UTCGHSA enrichment
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 16:27 UTCEPSS rescore
  26. 2026-07-06 16:26 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  27. 2026-07-06 04:51 UTCGHSA enrichment
  28. 2026-07-06 02:23 UTCEPSS rescore
  29. 2026-07-05 17:22 UTCGHSA enrichment
  30. 2026-07-05 05:54 UTCGHSA enrichment
  31. 2026-07-05 02:30 UTCEPSS rescore
  32. 2026-07-04 18:22 UTCGHSA enrichment
  33. 2026-07-04 06:54 UTCGHSA enrichment
  34. 2026-07-04 06:30 UTCEPSS rescore
  35. 2026-07-03 19:22 UTCGHSA enrichment
  36. 2026-07-03 07:54 UTCGHSA enrichment
  37. 2026-07-02 20:25 UTCGHSA enrichment
  38. 2026-07-02 08:57 UTCGHSA enrichment
  39. 2026-07-01 21:28 UTCGHSA enrichment
  40. 2026-07-01 15:06 UTCEPSS rescore
  41. 2026-07-01 15:06 UTCEPSS rescore
  42. 2026-07-01 10:00 UTCGHSA enrichment
  43. 2026-06-30 22:31 UTCEG score recompute
  44. 2026-06-30 22:31 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-36359?
CVE-2025-36359 is a medium vulnerability published on June 30, 2026. 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.
When was CVE-2025-36359 disclosed?
CVE-2025-36359 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-36359 actively exploited?
CVE-2025-36359 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-36359?
CVE-2025-36359 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.1.
How do I remediate CVE-2025-36359?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-36359, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-36359

Explore →

Is Your Infrastructure Affected by CVE-2025-36359?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs