Skip to main content
Report · SecurityWeekAbout CVE-2025-61882Published

Oracle E-Business Suite Zero-Day Exploited in Cl0p Attacks

Source SecurityWeek

0
Authoritative record:CVE-2025-61882· Critical 9.8

Exploited in the wild · KEV due 27 Oct 2025 · public exploit available (Metasploit) : apply the vendor's fix or mitigations to affected systems now.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 5 Oct 2025

  2. Weaponised: evidence found.

    1 Metasploit module

  3. Exploited in the wild: evidence found.

    Listed in CISA KEV 1 day after disclosure

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Oracle

    , 44 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 16 minutes after disclosure

  4. Added to CISA KEV (opens in a new tab)

    exploitation confirmed · ransomware use known

    , 1 day after disclosure

  5. KEV remediation due

    US federal deadline

    , 22 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

1. Immediate application of Oracle's official patches for CVE-2025-61882 across all affected Oracle EBS instances (versions 12.2.3 to 12.2.14) is critical. 2. Conduct thorough forensic investigations to detect any prior compromise or indicators of compromise using Oracle-provided IoCs and threat intelligence from Mandiant and GTIG. 3. Implement enhanced network segmentation and restrict access to Oracle EBS components, especially the BI Publishing Integration module, to trusted internal networks only. 4. Deploy advanced endpoint detection and response (EDR) solutions with behavioral analytics to identify anomalous activities indicative of exploitation attempts. 5. Enforce strict access controls and multi-factor authentication for all administrative and user accounts associated with Oracle EBS to prevent account compromise. 6. Monitor email systems for extortion or phishing campaigns linked to Cl0p and related groups, and educate employees on recognizing such threats. 7. Collaborate with incident response teams and share threat intelligence with relevant European cybersecurity agencies to stay updated on evolving tactics. 8. Review and harden Oracle EBS configurations, disable unnecessary services, and apply security best practices tailored to Oracle environments. 9. Prepare and test incident response plans specifically for ransomware and data breach scenarios involving Oracle EBS. 10. Consider deploying web application firewalls (WAF) and intrusion prevention systems (IPS) with signatures targeting exploitation attempts of this vulnerability.

Description

Oracle has informed customers that it has patched a critical remote code execution vulnerability tracked as CVE-2025-61882. The post Oracle E-Business Suite Zero-Day Exploited in Cl0p Attacks appeared first on SecurityWeek .

References

Community reviews

Loading reviews…