Siebel CrmApplication · Oracle

CVE-2026-46921

HIGH · 8.8 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to after 26.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Siebel CRM Cloud Applications product of Oracle Siebel CRM (component: Siebel Cloud Manager). Supported versions that are affected are 17.0-26.5. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Siebel CRM Cloud Applications. Successful attacks of this vulnerability can result in takeover of Siebel CRM Cloud Applications. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Unspecified vulnerability in Oracle Siebel CRM Cloud Applications Siebel Cloud Manager component allows low-privileged attackers with network access via HTTP to achieve complete takeover of the Siebel CRM application. The CVSS 3.1 score of 8.8 reflects high impacts across confidentiality, integrity, and availability with low attack complexity.

MitigationApply the Oracle Critical Patch Update addressing CVE-2026-46921 for Siebel CRM versions 17.0-26.5. As an immediate compensating control, restrict network access to Siebel Cloud Manager to trusted IP addresses and implement WAF rules for the HTTP endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Siebel CrmApplication
Affected:>= 17.0, <= 26.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Siebel Cloud Manager installation
    Review your Oracle Siebel CRM deployment documentation, cloud console, or installed software inventory to confirm whether the Siebel Cloud Manager component is deployed in your environment.
    Affected if Siebel Cloud Manager is present in the environment
  2. Check Siebel Cloud Manager version
    Access the Siebel Cloud Manager admin console or check the version information through the Siebel application management interface. The version is typically displayed in the About or System Information section of the Siebel Cloud Manager admin portal.
    Affected if The installed version falls within the range >= 17.0 and <= 26.5
  3. Verify network accessibility of Siebel Cloud Manager
    Determine if the Siebel Cloud Manager HTTP endpoints are exposed to network access. Check firewall rules, load balancer configurations, or API gateway settings to identify whether the management interface is reachable from network locations.
    Affected if Siebel Cloud Manager HTTP endpoints are accessible from untrusted or external network segments

Your environment is affected if Siebel Cloud Manager version 17.0 through 26.5 is installed AND the HTTP interface is reachable from network locations accessible to low-privileged attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 26.5
Interim mitigation

Apply the Oracle Critical Patch Update addressing CVE-2026-46921 for Siebel CRM versions 17.0-26.5. As an immediate compensating control, restrict network access to Siebel Cloud Manager to trusted IP addresses and implement WAF rules for the HTTP endpoints.

Fix this in Siebel Crm Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46921 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46921 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data