Skip to content
major vulnerability· requires attention

Affects Oracle Siebel CRM, a widely deployed enterprise CRM; allows unauthenticated adjacent-network attackers to fully compromise accessible CRM data.

Applications

CVE-2026-60757

8.1
High
EPSS 0.32%Patch availableAug 19, 2026

Unauthenticated adjacent-network attacker can modify or access Siebel CRM End User data.

common questions

Is CVE-2026-60757 being exploited?

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

How severe is CVE-2026-60757?

CVE-2026-60757 is rated High with a CVSS score of 8.1. 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-60757?

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

What does CVE-2026-60757 affect?

CVE-2026-60757 affects Oracle Siebel CRM End User (Search component) 17.0 - 26.6. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60757?

Isolate Siebel hosts, restrict network access, apply vendor patch/update immediately when available.

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

executive summary
technical analysis
affected
Oracle Siebel CRM End User (Search component) 17.0 - 26.6
impact

Adjacent-network unauthenticated attacker can create, delete, or modify all Siebel End User accessible data (C:H, I:H).

action required

Immediate action required

affected versions
Oracle Corporation Siebel CRM End User
  • affected>= 17.0 and <= 26.6

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