Oracle E-Business Suite flaw CVE-2026-46817 exploited as roughly 950 instances sit exposed online

Oracle E-Business Suite (EBS) customers are facing in-the-wild exploitation of CVE-2026-46817, a critical flaw in the File Transmission component of Oracle Payments. The issue lets an unauthenticated attacker compromise the module over HTTP, and it affects EBS releases 12.2.3 through 12.2.15. Oracle shipped a fix in its May 2026 Critical Security Patch Update, but exploitation began weeks later against systems that had not yet been updated.

What happened

Threat intelligence firm Defused reported on 29 June that its EBS decoy systems had recorded the first exploitation attempts over the preceding weekend, starting on 27 June. The activity came from a single source and looked like a targeted proof of concept rather than mass scanning, and it appeared before any public exploit code was available. On 1 July the Shadowserver Foundation said it had identified roughly 950 EBS instances exposed to the public internet, most of them in the United States, after improving its fingerprinting. Shadowserver did not assess how many of those systems remain unpatched. At the time of reporting, Oracle had not formally marked the flaw as exploited.

Technical details

  • The bug carries a CVSS score of 9.8 and stems from improper privilege management and missing authentication for a critical function.
  • Observed requests target the /OA_HTML/ibytransmit endpoint used by Oracle iPayment file transmission and were used to read local files on the server.
  • The same file-read primitive could expose configuration files holding database credentials, encryption keys or payment-processor API secrets.

Impact

EBS has become a recurring target for financially motivated actors: a different EBS flaw was mass-exploited by Cl0p in late 2025. Organisations running Oracle Payments on internet-facing EBS are at highest risk, because a successful attack could lead to theft of financial data and credentials that enable deeper compromise.

Recommendations

  • Apply the May 2026 Critical Security Patch Update (or later) to every EBS 12.2.3–12.2.15 environment.
  • Restrict EBS web interfaces to internal networks or VPN until patching is complete.
  • Review web logs for unexpected POST requests to /OA_HTML/ibytransmit.
  • Treat unpatched, internet-facing instances as potentially compromised; if suspicious activity is found, rotate database, application and payment-gateway credentials on the host.

Sources