Skip to content
major vulnerability· requires attention

Oracle Siebel is a widely used enterprise CRM; an unauthenticated network bug exposing admin data can lead to company-wide data breaches and cross-product impact.

Applications

CVE-2026-62586

8.6
High
EPSS 0.41%Patch availableAug 19, 2026

Unauthenticated HTTP flaw in Oracle Siebel CRM Admin allows full exposure of admin-accessible data.

common questions

Is CVE-2026-62586 being exploited?

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

How severe is CVE-2026-62586?

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

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

What does CVE-2026-62586 affect?

CVE-2026-62586 affects Oracle Siebel CRM Administration (Data Archival) 25.12-26.6, Siebel CRM. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62586?

Apply vendor patch if released; meanwhile restrict/deny HTTP access to Siebel Admin and monitor logs.

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

executive summary
technical analysis
affected
Oracle Siebel CRM Administration (Data Archival) 25.12-26.6Siebel CRM
impact

Unauthenticated remote attacker can access/exfiltrate all data reachable via Siebel CRM Administration (confidentiality compromise).

action required

Immediate action required

affected versions
Oracle Corporation Siebel CRM Administration
  • affected>= 25.12 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