Skip to content
Applications

CVE-2026-61097

9.6
Critical
EPSS 0.19%Patch availableJul 22, 2026

Unauthenticated HTTP vuln in Oracle Trade Finance allows data compromise and partial DoS.

common questions

Is CVE-2026-61097 being exploited?

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

How severe is CVE-2026-61097?

CVE-2026-61097 is rated Critical with a CVSS score of 9.6. 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-61097?

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

What does CVE-2026-61097 affect?

CVE-2026-61097 affects Oracle Financial Services - Oracle Banking Trade Finance Process Management 14.6.0 - 14.8.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61097?

Block public HTTP, apply vendor patch when released, deploy WAF and segment affected systems.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Oracle Financial Services - Oracle Banking Trade Finance Process Management 14.6.0 - 14.8.0
impact

Unauthenticated remote HTTP attacker (requires user interaction) can create/modify/delete or access all trade finance data and cause partial DoS.

action required

Immediate action required

affected versions
Oracle Corporation Oracle Banking Trade Finance Process Management
  • affected>= 14.6.0 and <= 14.8.0

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