Skip to content
major vulnerability· requires attention

Affects Oracle E-Business Suite (widely deployed ERP); high-impact data compromise risk to enterprise systems.

Applications

CVE-2026-60714

8.1
High
EPSS 0.34%Patch availableJul 22, 2026

Remote vulnerability in Oracle EBS Price Protection allowing data tampering and full module access.

common questions

Is CVE-2026-60714 being exploited?

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

How severe is CVE-2026-60714?

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

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

What does CVE-2026-60714 affect?

CVE-2026-60714 affects Oracle E-Business Suite - Price Protection 12.2.3 through 12.2.15. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60714?

Apply vendor patch when released; meanwhile restrict HTTP access, enforce network controls, audit 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 - Price Protection 12.2.3 through 12.2.15
impact

Low-privilege attacker via HTTP can create, delete, modify or fully access Oracle Price Protection data (C/I high).

action required

Immediate action required

affected versions
Oracle Corporation Oracle Price Protection
  • 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