Skip to content
major vulnerability· requires attention

Affects widely used enterprise middleware (IBM WebSphere); RCE can lead to full server compromise across many organizations.

Applications

CVE-2026-11536

HIGH
High
EPSS 0.34%Patch availableJul 31, 2026

RCE in IBM WebSphere SOAP/JMX connector (WAS 9.0 & 8.5).

common questions

Is CVE-2026-11536 being exploited?

Not confirmed. CVE-2026-11536 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.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-11536?

CVE-2026-11536 is rated High. 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-11536?

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

What does CVE-2026-11536 affect?

CVE-2026-11536 affects IBM WebSphere Application Server 9.0, IBM WebSphere Application Server 8.5. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-11536?

Apply vendor patch or disable/restrict SOAP/JMX; restrict network access to management interfaces.

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

executive summary
technical analysis
affected
IBM WebSphere Application Server 9.0IBM WebSphere Application Server 8.5
impact

Remote code execution via SOAP/JMX connector allowing attackers to run arbitrary code as the WebSphere process, enabling server compromise and data/control loss.

action required

Immediate action required

affected versions
IBM WebSphere Application Server
  • affected9.0
  • affected8.5

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