Skip to main content

Siebel CRM Deployment CVE-2026-91424

| EUVDEUVD-2026-106675 MEDIUM
Improper Access Control (CWE-284)
2026-10-20 secalert_us@oracle.com GHSA-h3r2-g49m-7hrm
6.4
CVSS 3.1 · Vendor: oracle
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with low-privilege Siebel account
  2. Exploit
    Send crafted HTTP requests to Server Infrastructure
  3. Execution
    Win timing/condition-dependent race (AC:H)
  4. Impact
    Crash deployment and tamper subset of data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires (1) network access to the Siebel CRM Deployment's Server Infrastructure component over HTTP, and (2) a valid low-privilege Siebel account (PR:L) - this is not unauthenticated. The High attack complexity (AC:H) indicates a further limiting condition the attacker does not fully control, such as a race/timing window or a specific server state that must coincide; this is the primary factor reducing real-world exploitability. Affected deployments are Oracle Siebel CRM 'Siebel CRM Deployment' versions 17.0 through 26.9. Realistic risk is highest where the Siebel server is internet- or widely-network-exposed and low-privilege accounts are liberally provisioned; it is substantially limited in environments where Siebel is restricted to an internal network and account issuance is tightly controlled. No end-user interaction is required (UI:N).

Impact

This is a moderate-severity, moderate-priority issue, not a top-tier emergency. The CVSS 3.1 base score of 6.4 (vector AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H) reflects a network-reachable flaw over HTTP, but two factors materially temper real-world risk: Attack Complexity is High (AC:H), meaning the attacker must win a race, meet timing constraints, or satisfy conditions outside their control, and Privileges Required is Low (PR:L), meaning a valid low-privilege Siebel account is a precondition. The dominant impact is Availability (A:H - complete, repeatable DoS/crash of the Siebel CRM Deployment), with only partial Confidentiality and Integrity impact (C:L/I:L - read of a subset of data and unauthorized insert/update/delete of some data). No EPSS score, no CISA KEV listing, and no public POC were provided in the input, so there is no signal of active or imminent exploitation - exploitation status is 'no public exploit identified at time of analysis.' No SSVC decision data was supplied. In short: the high CVSS-ish severity is driven by the complete-DoS availability impact, but the AC:H + PR:L gate makes opportunistic mass exploitation unlikely; this is a patch-in-normal-cycle item for Siebel operators rather than a drop-everything event, with priority rising for internet-exposed Siebel instances where low-privilege accounts are broadly provisioned.

Exploit ScenarioDerived

An authenticated low-privilege user (or an attacker who has phished/obtained such credentials) sends specially crafted HTTP requests to the Siebel Server Infrastructure component, exploiting a timing- or condition-dependent flaw (AC:H) to crash the deployment and/or tamper with a subset of accessible data. Because the service can be driven into a hang or repeatable crash, the attacker achieves a complete denial of service against the CRM platform. No public exploit code was identified at the time of analysis, and the High attack complexity means success is not guaranteed on a single attempt.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Oracle Siebel CRM Deployment releases 17.0 through 26.9 expose a Server Infrastructure weakness that lets a low-privilege user with HTTP access hang or repeatedly crash the component while also reading and modifying a limited subset of data it manages. The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H, base 6.4) shows the attack is remote but gated by a valid low-privilege Siebel account and by a high-complexity precondition such as a race window or a particular server state the attacker does not fully control, so the availability impact dominates (A:H) while confidentiality and integrity effects stay low. No public exploit code was identified at time of analysis and there is no CISA KEV confirmation of active exploitation; this is a moderate-severity, moderate-priority issue rather than a top-tier emergency, with the highest practical risk in deployments where the Siebel server is internet-facing or broadly reachable from the corporate network and low-privilege accounts are liberally provisioned.

RemediationAI

Oracle addressed this issue in the October 2026 Critical Patch Update, and the primary action is to apply that CPU to every Siebel CRM Deployment instance running a release in the 17.0 through 26.9 range, following the exact per-release fix versions published in the advisory at https://www.oracle.com/security-alerts/cpuoct2026.html (patch availability is per vendor advisory; no single universal fix version is stated in the available data). Where patching must be staged, reduce exposure by restricting network reachability to the Siebel Deployment Server Infrastructure HTTP endpoints to trusted administrative and application subnets, understanding that this breaks access for any legitimate remote users or integrations that terminate outside those ranges; and by tightening low-privilege account provisioning and auditing, since a valid low-privilege Siebel account is a hard prerequisite (PR:L) and the attack is not unauthenticated - this does not eliminate risk from already-provisioned users. Because exploitation depends on a high-complexity precondition, rehearsing the patched build in a staging Siebel environment first is low-cost relative to the downtime risk of the CPU itself. Monitor deployment-tier logs for repeated crashes, hangs, or restart loops of the Server Infrastructure component and treat clustered instances of them as a possible exploitation signal, and consider front-end request rate limiting or connection throttling as a stopgap, accepting that aggressive throttling degrades legitimate deployment and administrative operations.

Affected VersionsENISA

Siebel CRM Deployment 17.0 ≤26.9

Affected Packages

euvd siebel_crm_deployment no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Siebel CRM Deployment is the deployment/server-management tier of Oracle's Siebel CRM stack, and this issue sits in its Server Infrastructure component, reached over HTTP by whatever client or administrative traffic the deployment tier accepts. The CVSS vector AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H defines the practical shape of the flaw: reachable across the network, requiring an authenticated low-privilege principal, needing no victim interaction, and remaining within a single security scope, but carrying the High attack complexity flag that typically indicates a race condition, ordering dependency, or a specific internal server state (session, cache, queue, or configuration condition) that must coincide for the payload to land. No CWE identifier was supplied by the reporting source, so the exact root-cause class is not confirmed from available data; the impact pattern is a combined availability hit (complete denial of service through hangs or repeatable crashes of the deployment component) plus limited unauthorized read and limited insert/update/delete against data reachable through that component. Oracle CPU advisories do not publish per-CVE CPE mappings, so affected-product identification rests on the EUVD version range rather than on enumerated CPE strings.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (oracle) PRIMARY 6.4 MEDIUM
AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
vuln.today AI 6.4 MEDIUM

Network HTTP vector (AV:N) but a timing/condition-dependent flaw (AC:H) needing a valid low-privilege account (PR:L); complete DoS drives A:H with partial C:L/I:L data exposure and tampering.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (oracle).

CVSS VectorVendor: oracle

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

DescriptionCVE.org

Vulnerability in the Siebel CRM Deployment product of Oracle Siebel CRM (component: Server Infrastructure). Supported versions that are affected are 17.0-26.9. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Siebel CRM Deployment. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Siebel CRM Deployment as well as unauthorized update, insert or delete access to some of Siebel CRM Deployment accessible data and unauthorized read access to a subset of Siebel CRM Deployment accessible data. CVSS 3.1 Base Score 6.4 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H).

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Medium
Oracle Siebel is common legacy enterprise CRM, not universally deployed
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy