Skip to content
major vulnerability· requires attention

Affects widely used Oracle E-Business Suite; unauthenticated HTTP takeover with full control; high disruption risk.

ERP

CVE-2026-34275

9.8
Critical
EPSS 0.38%Patch availableApr 22, 2026

Unauthenticated remote takeover of Oracle Advanced Inbound Telephony.

common questions

Is CVE-2026-34275 being exploited?

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

How severe is CVE-2026-34275?

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

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

What does CVE-2026-34275 affect?

CVE-2026-34275 affects Oracle E-Business Suite – Oracle Advanced Inbound Telephony (Setup & Administration), v12.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-34275?

Patch when available; restrict HTTP access to Telephony; monitor logs

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 Inbound Telephony (Setup & Administration), v12.2.3-12.2.15
impact

Remote unauthenticated RCE via HTTP; attacker gains full control of Telephony component.

action required

Patch when possible

affected versions
Oracle Corporation Oracle Advanced Inbound 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