dbcve.org
Siebel CrmApplication · Oracle

CVE-2026-46885

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 Integration product of Oracle Siebel CRM (component: EAI). 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 Integration. Successful attacks of this vulnerability can result in takeover of Siebel CRM Integration. 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 · high confidence

Oracle Siebel CRM Integration EAI component contains a vulnerability exploitable via HTTP by low-privileged attackers, allowing complete takeover of the Siebel CRM Integration module. The CVSS vector indicates network-based exploitation with low attack complexity and no user interaction required, affecting versions 17.0 through 26.5.

MitigationApply the relevant Oracle Critical Patch Update for Siebel CRM or upgrade to a patched version. Prior to production deployment, test in a non-production environment to validate EAI functionality remains intact.

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 Oracle Siebel CRM installation and version
    Locate the Siebel installation directory and check the version file or use the Siebel application manager tool to retrieve the installed version number. Common locations include the SIEBEL_ROOT directory or check the application repository.
    Affected if The installed version falls within the range of 17.0 through 26.5 inclusive.
  2. Verify EAI component is configured
    Check the Siebel EAI (Enterprise Application Integration) component configuration through the Siebel Application Manager (SAM) or by reviewing the component definition in the Siebel repository database. Look for EAI object manager or integration objects.
    Affected if The EAI component is enabled and running in the Siebel environment.
  3. Confirm HTTP-based EAI interface is exposed
    Review the Siebel web server configuration and EAI HTTP services. Check if the EAI HTTP endpoints (such as /EAI_HTTP_Receiver or similar) are accessible through the web tier. Inspect the web.xml or ion.xml configuration files for exposed EAI servlets.
    Affected if HTTP access to the EAI component is enabled and exposed via the Siebel web server.
  4. Check for low-privileged user access
    Review the Siebel user administration to determine if low-privileged accounts exist with access to the EAI functionality. Verify if anonymous or low-privilege users can access integration workflows.
    Affected if Low-privileged users or anonymous accounts have permissions to invoke EAI HTTP services.

The environment is affected if Oracle Siebel CRM version 17.0 through 26.5 is installed with the EAI component enabled and accessible via HTTP to low-privileged users.

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 the relevant Oracle Critical Patch Update for Siebel CRM or upgrade to a patched version. Prior to production deployment, test in a non-production environment to validate EAI functionality remains intact.

Recommended fix Moderate confidence

Oracle Siebel CRM 26.6 or later (once patch is released)

  1. 1. Monitor Oracle Critical Patch Updates (CPUs) for the release of a security patch addressing CVE-2026-46885 for Siebel CRM
  2. 2. When patch is available, download from Oracle Support (support.oracle.com) using your Oracle SSO credentials
  3. 3. Review the patch readme and pre-install requirements
  4. 4. Apply the patch in a non-production environment first to validate
  5. 5. Schedule maintenance window and apply patch to production
  6. 6. Verify the patch was applied successfully and test EAI functionality
Caveat Review Oracle patch readme for any known issues or configuration changes required after patch application

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

Fix this in Siebel Crm Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46885 — 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-46885 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