Skip to content
major vulnerability· requires attention

Widely-used Oracle ERP component; remote low-privilege exploit could take over CMRO, disrupting many enterprises.

ERP

CVE-2026-46915

8.5
High
EPSS 0.32%Patch availableJun 17, 2026

Remote HTTP exploit enables takeover of Oracle CMRO (EBS).

common questions

Is CVE-2026-46915 being exploited?

Not confirmed. CVE-2026-46915 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-46915?

CVE-2026-46915 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-46915?

Yes. A fix has been recorded for CVE-2026-46915. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-46915 affect?

CVE-2026-46915 affects Oracle E-Business Suite CMRO Production (12.2.3-12.2.15). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46915?

Patch when available; restrict CMRO HTTP access; monitor for anomalous activity.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Oracle E-Business Suite CMRO Production (12.2.3-12.2.15)
impact

Remote attacker with network access and low privileges can takeover CMRO, compromising ERP data, controls, and availability.

action required

Patch when possible

affected versions
Oracle Corporation Oracle Complex Maintenance, Repair and Overhaul
  • affected>= 12.2.3 and <= 12.2.15

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free