Skip to content
major vulnerability· requires attention

Affects Oracle E-Business Suite (widely used ERP); enables remote low‑priv attacker to alter or access critical ERP data—high organizational impact.

ERP

CVE-2026-60871

8.1
High
EPSS 0.36%Patch availableJul 22, 2026

Oracle EBS Risk Management: remote low‑priv HTTP exploit allows full data modification/access.

common questions

Is CVE-2026-60871 being exploited?

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

How severe is CVE-2026-60871?

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

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

What does CVE-2026-60871 affect?

CVE-2026-60871 affects Oracle E-Business Suite (Oracle Risk Management) 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-60871?

Apply vendor patch/workaround ASAP; restrict HTTP access to EBS; audit and 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 Risk Management) 12.2.3-12.2.15
impact

Remote low‑privileged attacker via HTTP can create, delete, modify or fully access Oracle Risk Management data.

action required

Immediate action required

affected versions
Oracle Corporation Oracle Risk Management
  • 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