Skip to content
major vulnerability· requires attention

Remote, easily exploitable takeover of widely used enterprise CRM (Siebel) across many supported versions; high-impact, organization-wide disruption possible.

Applications

CVE-2026-60711

CRITICAL
Critical
EPSS 0.43%Patch availableJul 22, 2026

Remote takeover of Oracle Siebel CRM Cloud via HTTP

common questions

Is CVE-2026-60711 being exploited?

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

How severe is CVE-2026-60711?

CVE-2026-60711 is rated Critical. 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-60711?

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

What does CVE-2026-60711 affect?

CVE-2026-60711 affects Oracle Siebel CRM Cloud Applications, Siebel Cloud Manager, Versions 22.3–26.5. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60711?

Isolate Siebel Cloud Manager, block HTTP access to management interfaces, apply vendor patch ASAP

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

executive summary
technical analysis
affected
Oracle Siebel CRM Cloud ApplicationsSiebel Cloud ManagerVersions 22.3–26.5
impact

Low-privileged network attacker can remotely take over Siebel CRM Cloud Apps, causing full confidentiality, integrity and availability compromise and potential lateral impact.

action required

Immediate action required

affected versions
Oracle Corporation Siebel CRM Cloud Applications
  • affected>= 22.3 and <= 26.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