Oracle E-Business Suite's Patched 9.8 Flaw CVE-2026-101767 Is Already Under Exploratory Attack — Decoys Caught Attempts Seven Days After the CPU

Oracle E-Business Suite's Patched 9.8 Flaw CVE-2026-101767 Is Already Under Exploratory Attack — Decoys Caught Attempts Seven Days After the CPU

Oracle E-Business Suite's Patched 9.8 Flaw CVE-2026-101767 Is Already Under Exploratory Attack — Decoys Caught Attempts Seven Days After the CPU

Threat intelligence firm Defused Cyber reports that its Oracle E-Business Suite decoys recorded exploratory exploits against CVE-2026-101767 on the morning of October 27 — seven days after Oracle's October 20 Critical Patch Update shipped the fix, and roughly three months after Horizon3.ai privately reported the bug to Oracle on July 24. The flaw is a CVSS 9.8 improper authentication vulnerability in the Oracle Application Object Library layer of E-Business Suite, and the attack path is a chain: an unauthenticated SQL injection in the Thin Client Framework (TCF) servlet that escalates to remote code execution. Brandon Peterson, Jimi Sebree, and Noah King of Horizon3.ai are credited with the discovery.

The mechanics are classic legacy-ERP trouble. An attacker issues a crafted request to the TCF servlet at /OA_HTML/AppsTCFServer, which executes SQL with the privileges of the APPS database user; from there, the chain reaches operating-system command execution as the EBS application account. The blast radius depends on deployment: an intruder can read or modify application data accessible to APPS — depending on the instance, that can include financial, payroll, HR, and procurement records — and run host commands bounded by the EBS account's permissions. Internet-facing EBS deployments are the obvious risk, but Horizon3 warns internal instances are also exposed if an attacker can reach the servlet from a compromised system or another network segment.

What the exploit probes look like is unusually well documented. Defused's decoys caught the first-stage activity, and Horizon3's advisory lists the indicators: unauthenticated POST requests to /OA_HTML/AppsTCFServer that instantiate the Gantt data-server class (oracle.apps.jtf.gantt.server.GanttDataServer) followed by backend database activity; SQL reconnaissance — database version, current user, directory objects — immediately after unauthenticated web requests; and unexpected files in $APPLPTMP with the oracle account spawning /bin/sh through the Concurrent Manager to run OS commands. This is a vendor-tier web tier that many networks still trust by default, and the probe pattern gives defenders a concrete tripwire.

The patch-then-exploit cadence is the real story for defenders. EBS has been here before: over the past year, two other critical EBS flaws (CVE-2025-61882 and CVE-2026-46817, both 9.8) came under active exploitation, with the former leveraged by the Cl0p ransomware crew. Attackers increasingly treat the days right after a Critical Patch Update as a shopping window — the advisory reveals where the bug lives, and unpatched instances reveal who did not read it. We have watched the same window being worked against Atlassian's file-read flaw exploited within two days of disclosure and Oracle PeopleSoft under ShinyHunters-linked attack last month.

What Should You Do?

  1. Apply the October 2026 Critical Patch Update to every EBS instance — including internal ones; the decoy traffic proves the probing is automated and indiscriminate.
  2. If patching must wait, cut the servlet off at the edge — remove /OA_HTML/AppsTCFServer from the EBS URL firewall allowlist and restrict the EBS web tier to trusted networks; this is Horizon3's own interim guidance.
  3. Deploy the IoCs — alert on unauthenticated POSTs instantiating the Gantt data-server class, SQL recon following unauthenticated web requests, unexpected $APPLPTMP files, and Concurrent Manager shells; check whether any occurred before you patched.
  4. Inventory your ERP exposure honestly — if a 9.8 RCE on the EBS web tier took you by surprise, the problem is the inventory: enumerate internet-reachable ERP endpoints and put them on the patch SLA that matches their data sensitivity.

The WAF Angle

This story is one of the rare cases where the vendor's recommended workaround is a WAF action: pulling the TCF servlet out of the URL allowlist and gating the web tier to trusted networks is exactly the kind of request-path surgery a web application firewall does best while the real patch is staged. A WAF or reverse-proxy rule that blocks or flags unauthenticated POSTs to /OA_HTML/AppsTCFServer — especially those instantiating the Gantt data-server class — converts Horizon3's indicators into a live tripwire, and the same rule logic extends naturally to other servlet endpoints the ERP exposes but nobody actually uses. Legacy ERP is where the patch-gap pattern bites hardest: the software predates modern appsec assumptions, deployments linger for decades, and every Critical Patch Update hands attackers a fresh map of where to knock. The edge cannot patch for you, but it can hold the door while the patch catches up — the same reasoning we applied to GitLab's gateway flaw applies to a 1990s-era application suite with a 2026-grade RCE in it.

Sources