Skip to content
CRM

CVE-2026-70951

8.8
High
EPSS 0.30%Patch availableAug 19, 2026

Remote takeover of Oracle Siebel CRM End User via Document Management HTTP vulnerability.

common questions

Is CVE-2026-70951 being exploited?

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

How severe is CVE-2026-70951?

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

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

What does CVE-2026-70951 affect?

CVE-2026-70951 affects Oracle Siebel CRM End User (Document Management), Supported versions 17.0 through 26.6. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-70951?

Restrict HTTP access to Siebel, enable logging/monitoring, and apply vendor patch/workaround when released.

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 (Document Management)Supported versions 17.0 through 26.6
impact

Low‑privileged remote attacker can fully compromise Siebel CRM End User (C/I/A), enabling data theft, admin takeover, and service disruption.

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