# CVE-2026-60916: Missing authorization in Oracle WebCenter Enterprise Capture

> Unauthenticated attackers can modify, delete, or read critical data and cause partial denial of service in Oracle WebCenter Enterprise Capture.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-v454-h7f4-3h7r

## What is CVE-2026-60916?

CVE-2026-60916 is a critical missing authorization vulnerability in Oracle WebCenter Enterprise Capture, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle WebCenter Enterprise Capture product of Oracle Fusion Middleware (component: Client Bundle).  Supported versions that are affected are 12.2.1.4.0 and  14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebCenter Enterprise Capture.  While the vulnerability is in Oracle WebCenter Enterprise Capture, 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 WebCenter Enterprise Capture accessible data as well as  unauthorized read access to a subset of Oracle WebCenter Enterprise Capture accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle WebCenter Enterprise Capture. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Webcenter Enterprise Capture.

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

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

## Is CVE-2026-60916 being exploited?

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

## Other vulnerabilities in Oracle WebCenter Enterprise Capture

- [CVE-2026-46778](https://insights.sbomify.com/CVE-2026-46778/): Auth bypass in Oracle WebCenter Enterprise Capture (critical 10.0)
- [CVE-2026-46781](https://insights.sbomify.com/CVE-2026-46781/): Auth bypass in Oracle WebCenter Enterprise Capture (critical 10.0)
- [CVE-2026-60445](https://insights.sbomify.com/CVE-2026-60445/): Auth bypass in Oracle WebCenter Enterprise Capture (critical 9.9)
- [CVE-2026-60447](https://insights.sbomify.com/CVE-2026-60447/): Auth bypass in Oracle WebCenter Enterprise Capture (critical 9.9)
- [CVE-2026-60456](https://insights.sbomify.com/CVE-2026-60456/): Auth bypass in Oracle WebCenter Enterprise Capture (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60916 is a critical missing authorization vulnerability in Oracle WebCenter Enterprise Capture, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-60916 in the wild and no public exploit code.

Affected product: Oracle WebCenter Enterprise Capture. 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-60916/ (Markdown: https://insights.sbomify.com/CVE-2026-60916/index.md)
```

## Sources

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

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