Skip to content
major vulnerability· requires attention

Affects widely-used Oracle E-Business Suite; low-priv HTTP takeover could disrupt enterprise telephony.

ERP

CVE-2026-46947

8.8
High
EPSS 0.41%Patch availableJun 17, 2026

Low-priv attacker over HTTP can takeover Oracle Advanced Outbound Telephony.

common questions

Is CVE-2026-46947 being exploited?

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

How severe is CVE-2026-46947?

CVE-2026-46947 is rated High with a CVSS score of 8.8. 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-46947?

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

What does CVE-2026-46947 affect?

CVE-2026-46947 affects Oracle E-Business Suite - Oracle Advanced Outbound Telephony (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-46947?

Apply patch when available; restrict network access to telephony endpoints

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 - Oracle Advanced Outbound Telephony (12.2.3-12.2.15)
impact

Remote takeover of the telephony component with full C/I/A impact via HTTP by a low-priv attacker.

action required

Patch when possible

affected versions
Oracle Corporation Oracle Advanced Outbound Telephony
  • 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