Skip to content
major vulnerability· requires attention

Affects Oracle E-Business Suite ECCF (V15/V16); CVSS 9.9; widely deployed ERP; data compromise risk with partial DoS.

Web

CVE-2026-46897

9.9
Critical
EPSS 0.37%Patch availableJun 17, 2026

HTTP ECCF flaw enables low-privilege attacker to modify data and partial DoS.

common questions

Is CVE-2026-46897 being exploited?

Not confirmed. CVE-2026-46897 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.37% probability of exploitation in the next 30 days.

How severe is CVE-2026-46897?

CVE-2026-46897 is rated Critical with a CVSS score of 9.9. 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-46897?

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

What does CVE-2026-46897 affect?

CVE-2026-46897 affects Oracle E-Business Suite - Enterprise Command Center Framework (ECCF), V15 & V16. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46897?

Patch ASAP; restrict HTTP access to ECCF; enable monitoring.

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 - Enterprise Command Center Framework (ECCF), V15 & V16
impact

Unauthorized create/delete/modify of ECCF data; full data access; potential partial denial of service.

action required

Immediate action required

affected versions
Oracle Corporation Oracle Enterprise Command Center Framework
  • affectedV15
  • affectedV16

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