CVE-2025-36386

CVE-2025-36386 is a critical-severity vulnerability in Ibm Maximo Application Suite with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-305.

Key facts

Description

IBM Maximo Application Suite 9.0.0 through 9.0.15 and 9.1.0 through 9.1.4 could allow a remote attacker to bypass authentication mechanisms and gain unauthorized access to the application.

Frequently asked questions

What is CVE-2025-36386?
IBM Maximo Application Suite 9.0.0 through 9.0.15 and 9.1.0 through 9.1.4 could allow a remote attacker to bypass authentication mechanisms and gain unauthorized access to the application.
How severe is CVE-2025-36386?
CVE-2025-36386 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-36386 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-36386?
CVE-2025-36386 affects Ibm Maximo Application Suite. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-36386?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-36386 have an EU (EUVD) identifier?
Yes. CVE-2025-36386 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-36540.
When was CVE-2025-36386 published?
CVE-2025-36386 was published on 2025-10-28 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Ibm Maximo Application Suite

All CVEs affecting Ibm Maximo Application Suite →

Other CWE-305 vulnerabilities

Browse all CWE-305 vulnerabilities →