Affects Oracle E-Business Suite (widely deployed ERP); allows low-privilege network attacker to access and modify critical trade data, risking enterprise-wide data integrity/confidentiality.
CVE-2026-60875
Oracle EBS Trade Management flaw lets low-privilege remote attackers access and modify critical data.
Is CVE-2026-60875 being exploited?
Not confirmed. CVE-2026-60875 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-60875?
CVE-2026-60875 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-60875?
Yes. A fix has been recorded for CVE-2026-60875. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-60875 affect?
CVE-2026-60875 affects Oracle E-Business Suite - Trade Management (Claim LOV) 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-60875?
Apply vendor patch/workaround ASAP; restrict EBS HTTP access and audit logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote low-privilege attacker can create, delete, or modify Oracle Trade Management data, causing confidentiality and integrity compromise.
Immediate action required
- 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.