Siebel Apps MarketingApplication · Oracle

CVE-2026-46886

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 Apps - Marketing product of Oracle Siebel CRM (component: Marketing). 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 Apps - Marketing. Successful attacks of this vulnerability can result in takeover of Siebel Apps - Marketing. 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 Marketing component vulnerability allowing low-privileged attackers with network access via HTTP to achieve complete system compromise (full confidentiality, integrity, and availability impact). The flaw affects versions 17.0-26.5 and is easily exploitable, enabling complete takeover of the affected Marketing application.

MitigationApply Oracle's available security patches for the affected Siebel CRM versions (17.0-26.5) and consider network segmentation to restrict HTTP access to the Marketing component.

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 Apps MarketingApplication
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
    Locate Siebel installation directories or check for Siebel-related processes and services on the system. Common paths include C:\siebel or /siebel on Windows and Unix systems respectively.
    Affected if Oracle Siebel CRM is not installed on the system.
  2. Determine Siebel Marketing component version
    Query the Siebel application for its version number, typically accessible through the Siebel Administration interface, configuration files, or registry entries. Look specifically for the Marketing component version.
    Affected if The installed Marketing component version falls within range 17.0 to 26.5 inclusive.
  3. Verify HTTP listener configuration for Marketing
    Examine the Siebel web server configuration files (such as eapp.cfg, swe.cfg, or corresponding XML configuration) to determine if the Marketing component is configured to accept HTTP connections.
    Affected if HTTP listener is enabled and the Marketing component is accessible via HTTP protocol.
  4. Check network exposure of Marketing interface
    Review network configuration, firewall rules, or load balancer settings to determine if the Siebel Marketing interface is exposed to network access. Test connectivity to typical Siebel HTTP ports (usually 80, 443, 8080, or 8443).
    Affected if The Marketing component is reachable over the network via HTTP from untrusted locations.
  5. Confirm low-privilege user access exists
    Review Siebel user account configurations to determine if low-privileged accounts (non-administrator roles) exist and can authenticate to the Marketing component.
    Affected if Low-privileged user accounts have access to the Marketing application.

A system is affected if it runs Oracle Siebel CRM Marketing component versions 17.0 through 26.5 with HTTP access enabled and low-privileged user accounts can reach the Marketing interface.

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 Oracle's available security patches for the affected Siebel CRM versions (17.0-26.5) and consider network segmentation to restrict HTTP access to the Marketing component.

Fix this in Siebel Apps Marketing Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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