Skip to content
major vulnerability· requires attention

Oracle E-Business Suite is widely deployed; remote takeover of Payables can disrupt financial operations across organizations.

ERP

CVE-2026-61320

8.8
High
EPSS 0.43%Patch availableJul 22, 2026

Remote takeover of Oracle Payables in E-Business Suite 12.2.8–12.2.15.

common questions

Is CVE-2026-61320 being exploited?

Not confirmed. CVE-2026-61320 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-61320?

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

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

What does CVE-2026-61320 affect?

CVE-2026-61320 affects Oracle E-Business Suite - Oracle Payables 12.2.8-12.2.15. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61320?

Apply vendor patch immediately or isolate/restrict Payables HTTP access and monitor for misuse.

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 Payables 12.2.8-12.2.15
impact

Low-privileged attacker via HTTP can fully compromise Oracle Payables, access/modify financial records, and disrupt payments or financial workflows.

action required

Immediate action required

affected versions
Oracle Corporation Oracle Payables
  • affected>= 12.2.8 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