Skip to content
major vulnerability· requires attention

Affects IBM Engineering Lifecycle Management (enterprise software); unauthenticated access could lead to full compromise.

Applications

CVE-2026-3660

9.8
Critical
EPSS 0.58%Patch availableMay 27, 2026

Unauthenticated remote update of server properties in IBM ELM leads to unauthorized access.

common questions

Is CVE-2026-3660 being exploited?

Not confirmed. CVE-2026-3660 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.58% probability of exploitation in the next 30 days.

How severe is CVE-2026-3660?

CVE-2026-3660 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-3660?

Yes. A fix has been recorded for CVE-2026-3660. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-3660 affect?

CVE-2026-3660 affects IBM Engineering Lifecycle Management 7.0.3, IBM Engineering Lifecycle Management 7.1.0, IBM Engineering Lifecycle Management 7.2.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-3660?

Patch when available; limit exposure to trusted networks.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
IBM Engineering Lifecycle Management 7.0.3IBM Engineering Lifecycle Management 7.1.0IBM Engineering Lifecycle Management 7.2.0
impact

Remote, unauthenticated property-file update enables app access and data exposure.

action required

Immediate action required

affected versions
IBM Engineering Lifecycle Management
  • affected>= 7.0.3 and <= Interim Fix 021
  • affected>= 7.1.0 and <= Interim Fix 009
  • affected>= 7.2.0 and <= Interim Fix 001

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free