CVE-2026-46925
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. Difficult to exploit vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the 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.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:N/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 confidenceOracle Siebel CRM Cloud Applications (Siebel Cloud Manager component, versions 17.0-26.5) contains a difficult-to-exploit vulnerability allowing an unauthenticated attacker with physical access to the network segment attached to the hardware to compromise the application. The attack achieves complete confidentiality, integrity, and availability compromise leading to full takeover, with potential scope change affecting additional products.
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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:H/PR:N/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 if Oracle Siebel Cloud Manager is in useReview your Oracle Siebel deployment inventory or cloud service subscription documents to confirm the Siebel Cloud Manager component is deployed. Check Oracle billing or licensing records for 'Siebel Cloud Manager' or 'Siebel CRM Cloud Applications' subscriptions.Affected if The organization uses Oracle Siebel Cloud Manager as part of their Siebel CRM deployment.
-
Determine the installed Siebel Cloud Manager versionAccess the Siebel Cloud Manager admin console or contact Oracle Support to retrieve the current version number. The version is displayed in the About or System Information section of the Siebel Cloud Manager interface.Affected if The reported version falls within the range 17.0 through 26.5 inclusive.
-
Assess network segment and hardware accessibilityEvaluate whether the network segment and hardware hosting the Siebel environment could be accessed by unauthorized personnel. Review physical security controls, network isolation, and access logs for the data center or infrastructure hosting the Siebel Cloud Manager.Affected if The hardware and attached network segment lack adequate physical access controls, allowing potential unauthorized physical access.
The environment is affected if Oracle Siebel Cloud Manager versions 17.0-26.5 is deployed and the underlying hardware or network segment is accessible to unauthorized individuals.
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 dataSince this is a managed cloud product, contact Oracle Siebel support for the official patch. Implement strict physical access controls to the network infrastructure and hardware hosting the Siebel environment as an immediate compensating control while awaiting the vendor patch.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46925 — 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-46925 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