# CVE-2026-61271: Missing authorization in Oracle Document Management and Collaboration

> Unauthenticated attackers can read, modify, or delete data and cause partial denial of service in Oracle Document Management and Collaboration.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-4g9m-p6p6-252w

## What is CVE-2026-61271?

CVE-2026-61271 is a high-severity missing authorization vulnerability in Oracle Document Management and Collaboration, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Document Management and Collaboration product of Oracle E-Business Suite (component: Attachments).  Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Document Management and Collaboration.  Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Document Management and Collaboration accessible data as well as  unauthorized read access to a subset of Oracle Document Management and Collaboration accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Document Management and Collaboration. CVSS 3.1 Base Score 7.3 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Document Management and Collaboration.

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

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

## Is CVE-2026-61271 being exploited?

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

## Other vulnerabilities in Oracle Document Management and Collaboration

- [CVE-2026-83452](https://insights.sbomify.com/CVE-2026-83452/): Auth bypass in Oracle Document Management and Collaboration (critical 9.8)
- [CVE-2026-83454](https://insights.sbomify.com/CVE-2026-83454/): Privilege escalation in Oracle Document Management and Collaboration (high 8.8)
- [CVE-2020-2885](https://insights.sbomify.com/CVE-2020-2885/): Information disclosure in Document Management and Collaboration (high 8.2)
- [CVE-2021-2292](https://insights.sbomify.com/CVE-2021-2292/): Missing authorization in Document Management and Collaboration (high 8.1)
- [CVE-2021-2181](https://insights.sbomify.com/CVE-2021-2181/): Missing authorization in Document Management and Collaboration (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61271 is a high-severity missing authorization vulnerability in Oracle Document Management and Collaboration, published on 21 Jul 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-61271 in the wild and no public exploit code.

Affected product: Oracle Document Management and Collaboration. 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-61271/ (Markdown: https://insights.sbomify.com/CVE-2026-61271/index.md)
```

## Sources

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

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