Skip to content
major vulnerability· requires attention

Unauthenticated remote takeover in Oracle Siebel CRM (widely deployed enterprise CRM). CVSS 9.8 and network exploitability make this high-impact for many organizations.

Applications

CVE-2026-47036

9.8
Critical
EPSS 0.51%Patch availableJul 22, 2026

Unauthenticated remote takeover in Oracle Siebel CRM Approval Manager.

common questions

Is CVE-2026-47036 being exploited?

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

How severe is CVE-2026-47036?

CVE-2026-47036 is rated Critical with a CVSS score of 9.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-47036?

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

What does CVE-2026-47036 affect?

CVE-2026-47036 affects Oracle Siebel CRM Development (Siebel Approval Manager) v17.0-26.3, Siebel CRM servers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-47036?

Apply vendor patch immediately; block HTTP to Siebel, isolate servers, deploy WAF rules.

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

executive summary
technical analysis
affected
Oracle Siebel CRM Development (Siebel Approval Manager) v17.0-26.3Siebel CRM servers
impact

Unauthenticated HTTP exploit allows full Siebel CRM takeover (confidentiality, integrity, availability).

action required

Immediate action required

affected versions
Oracle Corporation Siebel CRM Development
  • affected>= 17.0 and <= 26.3

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