What is CVE-2025-61882?

CVE-2025-61882 is Oracle E-Business Suite Unspecified Vulnerability. The supplied enrichment data classifies it as Auth Bypass mapped to CWE-287 Improper Authentication.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

30 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, identity provider logs, authentication audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2025-61882 using CVSS 9.8, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: TraderTraitor (), Lazarus Group (), The Shadow Brokers (), FASTCash (), UTA0178 (), Ransomware use: Known. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVRansomwarecriticalAuth Bypasspublic exploit

CVE-2025-61882

CVE-2025-61882 — Oracle E-Business Suite Unspecified Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2025-61882 in CISA KEV with required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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).

Published Oct 5, 2025Updated Aug 4, 2026Sources: NVD, Oracle Corporation (CNA), CISA, FIRST EPSS, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Oct 6, 2025

EPSS

100%

top of FIRST's scoreset

Affects

Oracle

Oracle Concurrent Processing

CVSS base

9.8

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Oracle Concurrent Processing to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Federal deadline Oct 27, 2025 — passed 321 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Oracle	Oracle Concurrent Processing	12.2.3 to <= 12.2.14	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	Oracle (CNA), Oracle Corporation (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-91 · XML Injection (aka Blind XPath Injection)

Execute Unauthorized Code or Commands
Read Application Data
Modify Application Data::

Mitigation: Assume all input is malicious. Use an accept known good input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, boat may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as red or blue. Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.::

CWE-918 · Server-Side Request Forgery (SSRF)

Read Application Data
Execute Unauthorized Code or Commands::

Weakness & attack patterns

CWE-287Improper Authentication

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-151 · Identity SpoofingCAPEC-57 · Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-194 · Fake the Source of DataCAPEC-22 · Exploiting Trust in ClientCAPEC-650 · Upload a Web Shell to a Web ServerCAPEC-593 · Session HijackingCAPEC-114 · Authentication AbuseCAPEC-94 · Man in the Middle AttackCAPEC-633 · Token ImpersonationCAPEC-115 · Authentication Bypass

T1548Abuse Elevation Control Mechanism
T1040Network Sniffing
T1185Browser Session Hijacking

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Oct 6, 2025

Federal deadline

Oct 27, 2025

passed 321 days ago

Ransomware use

Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Malware

Families a CTI source ties to this CVE. One named, with the total it tracks.

Families tracked

Named

Cl0p

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

35 more posts on this CVEShowing 5 of 40 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Prioritize edge telemetry for network-reachable Oracle Concurrent Processing.
Monitor for scanner or exploit-pattern traffic after 30 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSidentity provider logsauthentication audit logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

TraderTraitorLazarus GroupThe Shadow BrokersFASTCashUTA0178

33 more threat groups on this CVEShowing 5 of 38 · Attribution, campaigns and the malware each one runsUnlock free

ip5.188.87.4020
Maltrail Malware Feeds · Sep 25, 2024
ip89.144.31.1837
URLhaus Feeds · Dec 7, 2025
hashaa0d3859d6633b62bccfb69017d33a8979a3be1f3f0a5a4bf6960d6c73d4112199
Computer Incident Response Center Luxembourg (CIRCL) · Oct 6, 2025
hashf90ac7ef934cb7d4d5e7f21338961727ca72fa6d99
SOCRadar Threat Exchange Services · Oct 7, 2025
hashb296d3b3115762096286f225696a9bb199
SOCRadar Threat Exchange Services · Oct 7, 2025

5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.8 (AV:N)
Aug 4, 2026 · NVD
2025
Added to CISA KEV catalog
Oct 6, 2025 · CISA
Initial · CVE published
Oct 5, 2025 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

15×SVRS was changedMar 6, 2026 – Aug 23, 2026 · SOCRadar CTI
10×TweetsFeb 27, 2026 – Jul 31, 2026 · SOCRadar CTI
2×Github ReposApr 19, 2026 – Jul 23, 2026 · SOCRadar CTI
2×TelegramMar 11, 2026 – May 17, 2026 · SOCRadar CTI
1×CVE modified by MITRE: CVSS metrics updated.Feb 26, 2026 · SOCRadar CTI

References

6 on the record

www.oracle.com/security-alerts/alert-cve-2025-61882.html
Vendor Advisory, Mitre, NIST, GITHUB
blogs.oracle.com/security/post/apply-july-2025-cpu
Vendor Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-61882
US Government Resource, NIST
www.crowdstrike.com/en-us/blog/crowdstrike-identifies-campaign-targeting-oracle-e-business-suite-zero-day-CVE-2025-61882/
Press/Media Coverage, NIST, GITHUB
labs.watchtowr.com/well-well-well-its-another-day-oracle-e-business-suite-pre-auth-rce-chain-cve-2025-61882well-well-well-its-another-day-oracle-e-business-suite-pre-auth-rce-chain-cve-2025-61882/
NIST, GITHUB
nvd.nist.gov/vuln/detail/CVE-2025-61882
Vendor Advisory

Coverage

15 stories from the feeds we poll

10 more reports on this CVEShowing 5 of 15 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Oracleevery CVE for this vendor
October 2025what else CISA listed
Auth Bypasssame class
CWE-287other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2025-61882 is Oracle E-Business Suite Unspecified Vulnerability, a critical vulnerability affecting Oracle Concurrent Processing from Oracle Corporation. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 30 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.