# CVE-2026-62637: Missing authorization in Oracle Reports Developer

> Unauthenticated attackers on the local network can read, create, delete, or modify critical data in Oracle Reports Developer.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-m93j-64hr-h2xw

## What is CVE-2026-62637?

CVE-2026-62637 is a critical missing authorization vulnerability in Oracle Reports Developer, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the Oracle Reports Developer product of Oracle Fusion Middleware (component: Security and Authentication).   The supported version that is affected is 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the Oracle Reports Developer executes to compromise Oracle Reports Developer.  While the vulnerability is in Oracle Reports Developer, 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 Reports Developer accessible data as well as  unauthorized access to critical data or complete access to all Oracle Reports Developer accessible data. CVSS 3.1 Base Score 9.3 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Reports Developer.

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

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

## Is CVE-2026-62637 being exploited?

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

## Other vulnerabilities in Oracle Reports Developer

- [CVE-2026-62608](https://insights.sbomify.com/CVE-2026-62608/): Auth bypass in Oracle Reports Developer (critical 9.9)
- [CVE-2026-62609](https://insights.sbomify.com/CVE-2026-62609/): Auth bypass in Oracle Reports Developer (critical 9.8)
- [CVE-2026-62611](https://insights.sbomify.com/CVE-2026-62611/): Auth bypass in Oracle Reports Developer (critical 9.8)
- [CVE-2026-62614](https://insights.sbomify.com/CVE-2026-62614/): Auth bypass in Oracle Reports Developer (critical 9.8)
- [CVE-2026-62617](https://insights.sbomify.com/CVE-2026-62617/): Auth bypass in Oracle Reports Developer (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62637 is a critical missing authorization vulnerability in Oracle Reports Developer, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62637 in the wild and no public exploit code.

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

## Sources

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

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