Skip to content
major vulnerability· requires attention

Widely-used enterprise CRM software; unauthenticated remote takeover threatens orgs; high visibility vulnerability.

CRM

CVE-2026-46889

9.8
Critical
EPSS 0.47%Patch availableJun 17, 2026

Unauthenticated HTTP exploit allows takeover of Siebel CRM Marketing.

common questions

Is CVE-2026-46889 being exploited?

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

How severe is CVE-2026-46889?

CVE-2026-46889 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-46889?

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

What does CVE-2026-46889 affect?

CVE-2026-46889 affects Oracle Siebel CRM Marketing (Marketing component), versions 17.0-26.5. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46889?

Patch/upgrade to fixed version when available; monitor HTTP traffic

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

executive summary
technical analysis
affected
Oracle Siebel CRM Marketing (Marketing component), versions 17.0-26.5
impact

Remote takeover via unauthenticated HTTP; attacker gains full control, data exposure, and service disruption.

action required

Immediate action required

affected versions
Oracle Corporation Siebel Apps - Marketing
  • affected>= 17.0 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