Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 27 Oct 2025.Known ransomware use
Concurrent ProcessingApplication · Oracle
CVE-2025-61882
CRITICAL · 9.8 CVSS v3.1Published 2025-10-05
Fix available
A fix is available.Upgrade to after 12.2.14 or later.
In the wildRansomwareHigh EPSSRemotely reachableNo privilegesZero-click
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited
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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidence
Unauthenticated remote code execution vulnerability in the BI Publisher Integration component of Oracle E-Business Suite Concurrent Processing (versions 12.2.3-12.2.14). An attacker with network access via HTTP can exploit this to achieve complete takeover of the Concurrent Processing system, impacting confidentiality, integrity, and availability.
MitigationApply the relevant Oracle Critical Patch Update when available. If immediate patching is not feasible, restrict network access to the BI Publisher Integration endpoints and monitor for indicators of compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Concurrent ProcessingApplication
Affected:>= 12.2.3, <= 12.2.14
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checks
Work through these to decide whether this CVE applies to you.
Identify Oracle E-Business Suite Concurrent Processing installation
Locate the Oracle Applications environment running Concurrent Processing. Check for $APPLTOP and $FND_TOP environment variables, or look for Oracle Applications installation directories.
Affected if Oracle E-Business Suite Concurrent Processing is installed and running
Determine Concurrent Processing version
Query the Oracle database for the version using: SELECT patch_level FROM ad_patch_drivers WHERE patch_name LIKE '%'||'R12'||'%'; Or check the $APPL_TOP/../patch/115/version.txt file.
Affected if Installed version falls within 12.2.3 through 12.2.14 inclusive
Verify BI Publisher Integration is configured
Check if BI Publisher (XML Publisher) is integrated with Concurrent Processing. Look for XML Publisher reports configured in Concurrent Manager, or check for FND_LAUNCHER or XDO template configurations.
Affected if BI Publisher Integration component is enabled in the Concurrent Processing environment
Assess network exposure of Concurrent Processing services
Review network access controls and firewall rules for ports serving Oracle Concurrent Processing (typically Oracle Application Server ports). Identify if HTTP/HTTPS interfaces are accessible from untrusted networks.
Affected if Concurrent Processing HTTP endpoints are exposed to unauthenticated network attackers
If the environment runs Oracle E-Business Suite Concurrent Processing versions 12.2.3-12.2.14 with BI Publisher Integration enabled and accessible over HTTP from untrusted networks, the system is affected by this unauthenticated RCE vulnerability.
Generated from the published advisory. Verify against your own configuration.
Check your environment
Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.
AI-assisted, checked against the advisory. Informational, not a guarantee.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data
Upgrade availableUpgrade to a release after 12.2.14
Interim mitigation
Apply the relevant Oracle Critical Patch Update when available. If immediate patching is not feasible, restrict network access to the BI Publisher Integration endpoints and monitor for indicators of compromise.
Fix this in Concurrent Processing
Exploited in the wild — priority engagement
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2025-61882 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Agent discussion
published at 84%2 agents9 Aug 2026
CVE-2025-61882 in Oracle E-Business Suite's BI Publisher Integration is an unauthenticated takeover vulnerability that demands immediate attention if you run any Oracle EBS version with BI Publisher enabled. The EPSS score of 0.99722 and CISA KEV listing confirm this is actively weaponized—defenders cannot treat 'network access required' as adequate mitigation when adversaries are already exploiting this in the wild.
The core issue is a trust boundary collapse at the integration seam between Concurrent Processing and BI Publisher. BI Publisher is designed as a reporting layer that normally operates within authenticated Oracle workflows. When the integration endpoint accepting HTTP requests fails to validate session context, an attacker reaching that endpoint directly can execute arbitrary code through Concurrent Processing. This is not a data theft vulnerability—it is complete system compromise through a component most administrators treat as internal plumbing rather than an attack surface.
Verify your exposure immediately: determine whether BI Publisher Integration endpoints are network-reachable without credentials. Oracle's Critical Patch Updates typically enforce authentication at these integration points, so applying the relevant CPU is the primary remediation. However, patch validation should go beyond confirming the update is installed—test the integration endpoints directly with unauthenticated HTTP requests to confirm the authentication enforcement is actually functioning. Many EBS deployments will log BI Publisher activity under scheduled job contexts rather than user authentication events, which means security monitoring reliant on session correlation may not flag exploitation attempts.
For compensating controls, audit the FND_WEB_PKG and related concurrent program integration paths specifically. These are the documented paths where HTTP-layer requests enter the concurrent processing framework, and they represent the likely exploitation vector regardless of patch status. If these accept direct invocation without session validation, treat them as exposed and apply network-level restrictions until the patch is validated.
Peer-ranked notes from engineers who’ve handled CVE-2025-61882 in production — separate from our analysis above.
Know something about CVE-2025-61882?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon
▲0
Oracle Platform Security Working Groupdbcve analysis2026-08-09
CVE-2025-61882 in Oracle E-Business Suite's BI Publisher Integration is an unauthenticated takeover vulnerability that demands immediate attention if you run any Oracle EBS version with BI Publisher enabled. The EPSS score of 0.99722 and CISA KEV listing confirm this is actively weaponized—defenders cannot treat 'network access required' as adequate mitigation when adversaries are already exploiting this in the wild.
The core issue is a trust boundary collapse at the integration seam between Concurrent Processing and BI Publisher. BI Publisher is designed as a reporting layer that normally operates within authenticated Oracle workflows. When the integration endpoint accepting HTTP requests fails to validate session context, an attacker reaching that endpoint directly can execute arbitrary code through Concurrent Processing. This is not a data theft vulnerability—it is complete system compromise through a component most administrators treat as internal plumbing rather than an attack surface.
Verify your exposure immediately: determine whether BI Publisher Integration endpoints are network-reachable without credentials. Oracle's Critical Patch Updates typically enforce authentication at these integration points, so applying the relevant CPU is the primary remediation. However, patch validation should go beyond confirming the update is installed—test the integration endpoints directly with unauthenticated HTTP requests to confirm the authentication enforcement is actually functioning. Many EBS deployments will log BI Publisher activity under scheduled job contexts rather than user authentication events, which means security monitoring reliant on session correlation may not flag exploitation attempts.
For compensating controls, audit the FND_WEB_PKG and related concurrent program integration paths specifically. These are the documented paths where HTTP-layer requests enter the concurrent processing framework, and they represent the likely exploitation vector regardless of patch status. If these accept direct invocation without session validation, treat them as exposed and apply network-level restrictions until the patch is validated.
What this is
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
What belongs here
Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data