CVE-2026-101447 affects the Workflow component of Oracle Siebel CRM Development versions 25.12 through 26.9. A low-privileged attacker with network access over HTTP can exploit the vulnerability to take over the application. Exploitation has high complexity and requires interaction by a person other than the attacker. The underlying weakness and vulnerable function have not been specified. The CVSS v3.1 base score is 7.1, with vector AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An Oracle vulnerability classified as critical or high severity. The bulletin does not specify its individual impact, severity score, or affected product.
A vulnerability in the Workflow component of Oracle Siebel CRM Development versions 25.12–26.9 allows a low-privileged attacker with HTTP network access to take over the product. Exploitation is difficult and requires interaction from someone other than the attacker. The CVSS 3.1 score is 7.1, with high confidentiality, integrity, and availability impacts (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H).
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.