CVE-2026-46926
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 · uneditedVulnerability 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 logon to the infrastructure where Siebel CRM Cloud Applications executes to compromise Siebel CRM Cloud Applications. While the vulnerability is in Siebel CRM Cloud Applications, attacks may significantly impact additional products (scope change). 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:L/AC:L/PR:L/UI:N/S:C/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 confidenceLocal privilege escalation vulnerability in Oracle Siebel CRM Cloud Applications (Siebel Cloud Manager component) allows a low-privileged attacker with physical or terminal access to the underlying infrastructure to compromise the application. The vulnerability enables complete takeover of Siebel CRM Cloud Applications and may impact additional products due to scope change.
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>= 17.0, <= 26.5CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Siebel Cloud Manager installationSearch for Siebel Cloud Manager processes or installed components on the system. Check for directories or services named 'Siebel' or 'SiebelCloudManager'. Use commands like 'sc query' on Windows or 'ps aux | grep -i siebel' on Linux to find running processes.Affected if Siebel Cloud Manager is found running on the system
-
Determine installed Siebel Cloud Manager versionCheck the version of the installed Siebel Cloud Manager. Common locations include: installation directories, registry keys (Windows), or version files in the application directory. Compare the version number against the affected range 17.0 to 26.5.Affected if The installed version falls within 17.0 through 26.5 inclusive
-
Verify local infrastructure access existsAssess whether low-privileged users have local or physical access to the infrastructure hosting Siebel Cloud Manager. Check for shared access, console access, or multi-user system configurations where untrusted local users exist.Affected if Untrusted or low-privileged local accounts have access to the Siebel Cloud Manager host
-
Check for privilege boundary configurationsReview user account configurations and group memberships on the Siebel Cloud Manager system. Identify if any unprivileged accounts exist that could potentially leverage a local privilege escalation.Affected if Low-privileged or untrusted local accounts are present on the system hosting Siebel Cloud Manager
The environment is affected if Siebel Cloud Manager versions 17.0 through 26.5 are installed and low-privileged users have local infrastructure access to the host system.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle's available patches for the affected versions (17.0-26.5). Restrict and monitor local/terminal access to the infrastructure where Siebel CRM Cloud Applications executes, as this is a local attack vector requiring logon access.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46926 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46926 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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