# CVE-2026-61107: Privilege escalation in Oracle Applications DBA

> High-privileged attackers can escalate privileges to take over Oracle Applications DBA via network access.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 1 Aug 2026
- **Also known as:** GHSA-wc95-cpqw-g35c

## What is CVE-2026-61107?

CVE-2026-61107 is a high-severity vulnerability in Oracle Applications DBA, published on 21 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the Oracle Applications DBA product of Oracle E-Business Suite (component: Internal Operations).  Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Applications DBA.  Successful attacks of this vulnerability can result in takeover of Oracle Applications DBA. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Oracle Applications Dba.

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

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

## Is CVE-2026-61107 being exploited?

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

## Other vulnerabilities in Oracle Applications DBA

- [CVE-2026-61110](https://insights.sbomify.com/CVE-2026-61110/): Auth bypass in Oracle Applications DBA (high 8.8)
- [CVE-2026-22011](https://insights.sbomify.com/CVE-2026-22011/): Privilege escalation in Oracle Applications DBA (high 7.6)
- [CVE-2026-70681](https://insights.sbomify.com/CVE-2026-70681/): Auth bypass in Oracle Applications DBA (high 7.5)
- [CVE-2026-70680](https://insights.sbomify.com/CVE-2026-70680/): Missing authorization in Oracle Applications DBA (high 7.1)
- [CVE-2026-60761](https://insights.sbomify.com/CVE-2026-60761/): Missing authorization in Oracle Applications DBA (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61107 is a high-severity vulnerability in Oracle Applications DBA, published on 21 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61107 in the wild and no public exploit code.

Affected product: Oracle Applications DBA. 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-61107/ (Markdown: https://insights.sbomify.com/CVE-2026-61107/index.md)
```

## Sources

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

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