dbcve.org
Siebel CrmApplication · Oracle

CVE-2026-46919

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to after 26.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 unauthenticated 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 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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

Unauthenticated remote code execution vulnerability in Oracle Siebel CRM Cloud Applications' Siebel Cloud Manager component. The flaw is network-exploitable via HTTP with no authentication required, allowing attackers to gain full system takeover.

MitigationApply Oracle's latest security patch for Siebel CRM Cloud Applications; upgrade to a version beyond 26.5 if available. If immediate patching is not possible, restrict network access to Siebel Cloud Manager interfaces via firewall or VPN.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 if Siebel Cloud Manager is deployed
    Review your Oracle Siebel CRM installation inventory or configuration documentation to determine if the Siebel Cloud Manager component is present in your environment.
    Affected if Siebel Cloud Manager component is not installed or not in use (not affected). If it is installed, continue to next checks.
  2. Determine the installed Siebel Cloud Manager version
    Access the Siebel Cloud Manager admin interface or check the installation directory for version information. Use the component's built-in version command or consult Oracle Enterprise Manager for the installed version number.
    Affected if The installed version falls within the range >= 17.0 AND <= 26.5 (potentially affected). Versions outside this range are not affected.
  3. Verify if Siebel Cloud Manager HTTP interface is network-accessible
    From an external network location, attempt to reach Siebel Cloud Manager endpoints via HTTP (port 80/443) or check firewall rules and load balancer configurations that expose this component to network traffic.
    Affected if The Siebel Cloud Manager interface is reachable via HTTP from untrusted networks (potentially affected). If it is only accessible from trusted internal networks, the external exploit risk is reduced but the vulnerability may still exist.
  4. Check if unauthenticated access is permitted
    Review Siebel Cloud Manager authentication configuration and access control settings. Determine whether the HTTP endpoints allow requests without valid authentication credentials.
    Affected if Unauthenticated HTTP requests to Siebel Cloud Manager are permitted (vulnerable condition present). If authentication is required for all endpoints, the specific exploitation path may be blocked.

A user is affected if they have Oracle Siebel Cloud Manager installed with a version between 17.0 and 26.5 and the component's HTTP interface is network-accessible without authentication.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 26.5
Interim mitigation

Apply Oracle's latest security patch for Siebel CRM Cloud Applications; upgrade to a version beyond 26.5 if available. If immediate patching is not possible, restrict network access to Siebel Cloud Manager interfaces via firewall or VPN.

Recommended fix Moderate confidence

Contact Oracle Support for the specific CPU containing the fix for this vulnerability (versions beyond 26.5 or the corresponding CPU release)

  1. 1. Identify the current installed version of Siebel Cloud Manager by checking the Siebel deployment documentation or enterprise manager.
  2. 2. Contact Oracle Support to obtain the Critical Patch Update (CPU) that addresses CVE-2026-46919, as Oracle typically remediates Siebel vulnerabilities through quarterly CPU releases.
  3. 3. Apply the Oracle CPU containing the fix for this vulnerability in a non-production environment first to validate compatibility.
  4. 4. After testing, schedule a maintenance window and apply the CPU to production environments.
  5. 5. Verify the patch was applied successfully by checking the Siebel Cloud Manager version and confirming the vulnerability is resolved.
  6. 6. Review Oracle's related security alerts and documentation for any additional required configurations post-patch.
Caveat Oracle CPU patches typically include cumulative fixes; review Oracle pre-install requirements and test thoroughly in a non-production environment before applying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Siebel Crm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-46919 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