Unauthenticated, network-accessible vulnerability in widely deployed Oracle Siebel CRM allowing full compromise/modification of critical CRM data (CVSS 9.3); can disrupt business operations across organizations.
CVE-2026-70855
Critical unauthenticated remote vulnerability in Oracle Siebel Self Service enabling full data compromise.
Is CVE-2026-70855 being exploited?
Not confirmed. CVE-2026-70855 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.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-70855?
CVE-2026-70855 is rated Critical with a CVSS score of 9.3. 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-70855?
Not known from our data. No patch reference has been recorded for CVE-2026-70855, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-70855 affect?
CVE-2026-70855 affects Oracle Siebel CRM - Self Service 17.0 to 26.6. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70855?
Isolate/block public Siebel HTTP endpoints, apply vendor patch/mitigations when released, enforce MFA and monitor logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated HTTP exploit (requires user interaction) permits attackers to create, delete, modify or fully access Siebel App data; scope may affect other products.
Immediate action required
- 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.