Skip to content
major vulnerability· requires attention

Affects Oracle E-Business Suite (widely used enterprise ERP); allows takeover of a core component and risks broad business impact.

ERP

CVE-2026-60789

8.8
High
EPSS 0.43%Patch availableJul 22, 2026

High-severity takeover of Oracle E-Business Suite Sales Offline (12.2.3–12.2.15).

common questions

Is CVE-2026-60789 being exploited?

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

How severe is CVE-2026-60789?

CVE-2026-60789 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-60789?

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

What does CVE-2026-60789 affect?

CVE-2026-60789 affects Oracle E-Business Suite - Oracle Sales Offline 12.2.3-12.2.15, Oracle EBS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60789?

Block/limit HTTP access to Sales Offline, isolate instances, apply vendor patch when released, 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 Sales Offline 12.2.3-12.2.15Oracle EBS
impact

Low-privileged attacker with HTTP access can fully compromise Oracle Sales Offline, enabling data theft, integrity loss, and downtime.

action required

Immediate action required

affected versions
Oracle Corporation Oracle Sales Offline
  • 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