# CVE-2025-61757: Oracle Fusion Middleware Missing Authentication for Critical Function

> Unauthenticated attackers can compromise Oracle Identity Manager via HTTP, leading to full system takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 21 Nov 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-v5gw-cq42-m6w2

## What is CVE-2025-61757?

CVE-2025-61757 is a critical authentication bypass vulnerability in Oracle Corporation Identity Manager, published on 21 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Identity Manager product of Oracle Fusion Middleware (component: REST WebServices).  Supported versions that are affected are 12.2.1.4.0 and  14.1.2.1.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Identity Manager.  Successful attacks of this vulnerability can result in takeover of Identity Manager. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-61757?

It affects 1 product.


Products: Oracle Identity Manager.

## How do I fix CVE-2025-61757?

No fix has been published for CVE-2025-61757 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 12 Dec 2025.

## Is CVE-2025-61757 being exploited?

Yes. Attackers have exploited CVE-2025-61757 in the wild since at least 21 Nov 2025.

Public exploit code:

- Oracle Identity Manager 远程代码执行漏洞CVE-2025-61757 (github_poc): https://github.com/Jinxia62/Oracle-Identity-Manager-CVE-2025-61757
- CVE-2025-61757 (github_poc): https://github.com/ngominhquocngu/Blackash-CVE-2025-61757
- Oracle Identity Manager REST WebServices - Authentication Bypass (nuclei): http/cves/2025/CVE-2025-61757.yaml

## Other vulnerabilities in Oracle Corporation Identity Manager

- [CVE-2017-10151](https://insights.sbomify.com/CVE-2017-10151/): Auth bypass in Identity Manager (critical 10.0)
- [CVE-2026-60720](https://insights.sbomify.com/CVE-2026-60720/): Auth bypass in Oracle Identity Manager (critical 9.9)
- [CVE-2026-61066](https://insights.sbomify.com/CVE-2026-61066/): Auth bypass in Oracle Identity Manager (critical 9.9)
- [CVE-2026-35268](https://insights.sbomify.com/CVE-2026-35268/): Auth bypass in Identity Manager (critical 9.9)
- [CVE-2026-35294](https://insights.sbomify.com/CVE-2026-35294/): Auth bypass in Identity Manager Connector (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61757 and fix it if it is affected.

What it is: CVE-2025-61757 is a critical authentication bypass vulnerability in Oracle Corporation Identity Manager, published on 21 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-61757 in the wild since at least 21 Nov 2025.

Affected product: Oracle Corporation Identity Manager. 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-2025-61757/ (Markdown: https://insights.sbomify.com/CVE-2025-61757/index.md)
```

## Sources

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

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