# CVE-2026-61097: Cross-site request forgery in Oracle Banking Trade Finance Process Management

> Unauthenticated attackers can exploit CSRF to modify or access critical banking data and cause partial denial of service.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-gcw7-hq6v-5f6g

## What is CVE-2026-61097?

CVE-2026-61097 is a critical vulnerability in Oracle Banking Trade Finance Process Management, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Banking Trade Finance Process Management product of Oracle Financial Services Applications (component: Common).  Supported versions that are affected are 14.6.0-14.8.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Banking Trade Finance Process Management.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Banking Trade Finance Process Management, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized creation, deletion or modification access to critical data or all Oracle Banking Trade Finance Process Management accessible data as well as  unauthorized access to critical data or complete access to all Oracle Banking Trade Finance Process Management accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Banking Trade Finance Process Management. CVSS 3.1 Base Score 9.6 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L).

Weakness: CWE-601 (URL Redirection to Untrusted Site), CWE-352 (Cross-Site Request Forgery), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-61097?

It affects 1 product.


Products: Oracle Banking Trade Finance Process Management.

## How do I fix CVE-2026-61097?

No fix has been published for CVE-2026-61097 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61097 being exploited?

There is no known exploitation of CVE-2026-61097 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Banking Trade Finance Process Management

- [CVE-2022-21474](https://insights.sbomify.com/CVE-2022-21474/): Missing authorization in Banking Trade Finance (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61097 and fix it if it is affected.

What it is: CVE-2026-61097 is a critical vulnerability in Oracle Banking Trade Finance Process Management, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-61097 in the wild and no public exploit code.

Affected product: Oracle Banking Trade Finance Process Management. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61097/ (Markdown: https://insights.sbomify.com/CVE-2026-61097/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61097
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61097
- OSV: https://osv.dev/vulnerability/CVE-2026-61097

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61097/
Summaries are generated and may contain mistakes; the official description above is the record.