# CVE-2025-61882: Oracle E-Business Suite Unspecified

> Unauthenticated attackers can compromise Oracle Concurrent Processing 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 6 Oct 2025 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2025
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-hgff-wp2m-jgfw

## What is CVE-2025-61882?

CVE-2025-61882 is a critical authentication bypass vulnerability in Oracle Concurrent Processing, published on 5 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Concurrent Processing product of Oracle E-Business Suite (component: BI Publisher Integration).  Supported versions that are affected are 12.2.3-12.2.14. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Concurrent Processing.  Successful attacks of this vulnerability can result in takeover of Oracle Concurrent Processing. 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-287 (Improper Authentication)

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

It affects 1 product.


Products: Oracle Concurrent Processing.

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

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

## Is CVE-2025-61882 being exploited?

Yes. Attackers have exploited CVE-2025-61882 in the wild since at least 6 Oct 2025, including in ransomware campaigns.

Public exploit code:

- https://github.com/watchtowrlabs/watchTowr-vs-Oracle-E-Business-Suite-CVE-2025-61882 (github_poc): https://github.com/watchtowrlabs/watchTowr-vs-Oracle-E-Business-Suite-CVE-2025-61882
- Detection for CVE-2025-61882 & CVE-2025-61884 (github_poc): https://github.com/rxerium/CVE-2025-61882-CVE-2025-61884
- https://github.com/zerozenxlabs/CVE-2025-61882-Oracle-EBS (github_poc): https://github.com/zerozenxlabs/CVE-2025-61882-Oracle-EBS
- A critical pre-authentication Remote Code Execution (RCE) flaw in Oracle E-Business Suite (versions 12.2.3 - 12.2.14) allows attackers to gain full control over vulnerable servers via malicious HTTP requests - now actively exploited in the wild. (github_poc): https://github.com/AdityaBhatt3010/CVE-2025-61882-Oracle-E-Business-Suite-Pre-Auth-RCE-Exploit
- Exploit for CVE-2025-61882 (do not use without any written permission).  (github_poc): https://github.com/Sachinart/CVE-2025-61882
- Detects Oracle E-Business Suite (CVE-2025-61882). Detection: multi-tier checks — fingerprinting, version checks, endpoint & SSRF tests, timing analysis & controlled exploitation 4 high-confidence results. Default = safe fingerprinting only. Set aggressive=true 2 enable active/probing checks use w/caution. Provided By BattalionX BattalionX@proton.me (github_poc): https://github.com/BattalionX/http-oracle-ebs-cve-2025-61882.nse

## Other vulnerabilities in Oracle Concurrent Processing

- [CVE-2021-2295](https://insights.sbomify.com/CVE-2021-2295/): Missing authorization in Concurrent Processing (high 8.1)
- [CVE-2024-21089](https://insights.sbomify.com/CVE-2024-21089/): Information disclosure in Concurrent Processing (medium 6.5)
- [CVE-2026-61051](https://insights.sbomify.com/CVE-2026-61051/): Missing authorization in Oracle Concurrent Processing (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61882 is a critical authentication bypass vulnerability in Oracle Concurrent Processing, published on 5 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-61882 in the wild since at least 6 Oct 2025, including in ransomware campaigns.

Affected product: Oracle Concurrent Processing. 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-61882/ (Markdown: https://insights.sbomify.com/CVE-2025-61882/index.md)
```

## Sources

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

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