Tuesday, November 17, 2026

Oracle Critical Security Patch Update Advisory - November 2026

 

Oracle’s November 2026 CSPU:

Oracle’s November 2026 Critical Security Patch Update (released 17 November) delivers 655 new patches. The count matters less than the timing. This post covers what’s in the patch for E-Business Suite (EBS), the SOA and middleware layer, and the governance work around it. It also covers how this week’s attacks change the order in which you should do things.

  • EBS: 71 patches, 19 unauthenticated-remote. Fusion Middleware: 71 patches, 53 unauthenticated-remote. Database: 7 patches, 3 unauthenticated-remote.
  • Oracle’s advisory doesn’t flag any of these CVEs as exploited. None of the incidents I found this week involve them either. But Oracle estates have been hit repeatedly by attackers working from patch-to-exploit timelines, so assume the clock is running.
  • Rank by exposure first, CVSS second. A 9.8 on an internet-facing EBS tier outranks a 9.9 that needs a database session.
  • The patch is only half the work. This week’s incidents point at your third-party scripts, update channels and exposed secrets, which the CSPU doesn’t touch.

What happened this week, and why it matters to an Oracle estate

Several incidents this week matter to anyone running EBS, SOA or WebLogic. Some come from aggregator trackers, so I’ve flagged where details are unverified.

IncidentWhat happenedLesson for your estate
Optimizely supply-chain attack (Nov 16)Researchers say malicious code served through the Optimizely website-testing platform reached 178 organizations, letting criminals skim payment card numbers and crypto payments from visitors. Report URI said nearly all of the infected scripts it was tracking had been cleaned by that evening. Optimizely said it blocked the vulnerable path and deployed a fix, and Equifax said it found no evidence its own systems were compromised.The victims’ own systems weren’t breached. A trusted third-party script was. If iStore, iSupplier or any customer-facing EBS page loads external JavaScript, you have the same exposure.
cPGuard update channel hijack (Nov 2)Attackers broke into the update system of a security tool on November 2 and pushed a malicious script to customers’ Linux servers that installed a backdoor and collected password hashes.Your patch pipeline and agent update channels are an attack path. Verify signatures and checksums on everything, including Oracle media.
AI-agent-driven intrusionsGitBook confirmed a targeted attack accessed some infrastructure credentials, though the AI-agent detail is unverified. A threat-intel report claims an autonomous agent registered at least 1,438 accounts on a scanning service to hunt exposed .env files and validate stolen AI API keys. That second claim comes from one vendor report.Attackers are automating credential discovery at scale. Secrets in repos, .env files, integration configs and ISG service accounts are the soft target.
Edge and gateway exploitation (Nov 10–13)CISA added a Barracuda Email Security Gateway pair that chains an auth bypass with command injection to give root, plus an exploited Chrome use-after-free, to its KEV catalog on Nov 10. An UnrealIRCd command-injection flaw was added too.Attackers keep going after internet-facing infrastructure and chaining flaws. Think about chains, not single CVEs.
Third-party disclosuresA November 13 Uber disclosure has intensified concern over third-party security.Fourth-party risk is now a board topic. Major Cyberattack Targets 178 Organizations, Millions of Credit Card Users at Risk +8

The Oracle-specific backdrop

Oracle estates are a proven target, and the history sets expectations for the next 30 days:

  • The Clop extortion gang exploited an EBS zero-day (CVE-2025-61882, CVSS 9.8) against multiple victims, including US universities. One report says the group stole data from more than 100 organizations. Extortion demands ranged from millions up to $50 million in at least one case. www.bleepingcomputer.com +3
  • Oracle mitigated a PeopleSoft zero-day (CVE-2026-35273) that ShinyHunters exploited for unauthenticated remote code execution between May 27 and June 9. CISA also flagged a WebLogic flaw (CVE-2024-21182) as actively exploited two years after it was patched. Bleeping ComputerBleeping Computer
  • Another EBS flaw, CVE-2026-46817 (9.8, unauthenticated HTTP takeover), was seen exploited on honeypots before Oracle had flagged it as exploited. Bleeping Computer
  • CISA has listed 44 Oracle vulnerabilities as exploited, 13 of which were also abused by ransomware gangs. Bleeping Computer

The pattern is consistent. Attackers hit unauthenticated HTTP paths in EBS, PeopleSoft and WebLogic, steal data, then extort. Data theft, not encryption, is the main business risk. That should shape your priorities.

The architect’s read of the CSPU: think in chains

A CVSS list tells you what’s broken. An architect asks what an attacker can reach from the internet and what they can pivot to. Here is the November advisory as a chain:

Edge → web tier → application → middleware → database

  1. Edge and web tier. Oracle HTTP Server’s WebLogic proxy plug-in (curl component, CVE-2026-9545, 7.5, unauthenticated, HTTPS) sits in front of many EBS deployments. APEX and ORDS also carry CVE-2026-114849 (9.8, unauthenticated, HTTPS), and APEX has a second 9.8 (CVE-2026-114850). Many EBS shops run APEX or ORDS for side applications, and they’re easy to overlook in an EBS-focused patch plan. CVE-2026-114849 also credits several researchers working with Trend Micro’s Zero Day Initiative. That is my inference, not Oracle’s, but multiple independent reporters suggest more people have looked at this bug.
  2. Application tier. The four unauthenticated 9.8s in EBS (Attachments, AOL Core, OAF REST Services, Universal Work Queue media integration), plus Mobile Field Service Admin UI (CVE-2026-101691, 9.3).
  3. Middleware. WebLogic (TopLink at 10.0 and 9.8, T3/IIOP and SOAP at 9.8), Oracle Platform Security for Java (10.0) and Access Manager (three 10.0s). A foothold here reaches EBS, SOA and everything else on the domain.
  4. Management plane. Enterprise Manager’s Agent Next Gen has a Jetty issue (CVE-2026-10050, 9.1, unauthenticated). If OEM manages your EBS and database, it is a lateral-movement path.
  5. Database. Three 9.9 flaws need only Create Session. After an application-tier compromise, that is easy to obtain.

The attacker doesn’t care which product family a CVE sits in, so your patch groups shouldn’t either. Treat the EBS + OHS + WebLogic + OAM + database + OEM group as one release.

EBS deep dive

Tier-0 EBS items (unauthenticated, network):

CVEModuleScore
CVE-2026-114880Document Mgmt & Collaboration, Attachments9.8
CVE-2026-114924Application Object Library, Core9.8
CVE-2026-114925Applications Framework, REST Services9.8
CVE-2026-114863Universal Work Queue, Media Integration9.8
CVE-2026-101691Mobile Field Service, Admin UI9.3 (scope changed)
CVE-2026-114881Document Mgmt & Collaboration, Attachments9.1
CVE-2026-114876iStore, Shopping Cart8.6 (scope changed)

What the module spread tells you:

  • Customer- and supplier-facing modules (iStore, iProcurement, Sourcing, Mobile Field Service) carry several unauthenticated issues. If you publish any of these through an external tier, they go to the front of the queue.
  • Purchasing (9), iProcurement (7) and Sales Online (6) are mostly authenticated flaws at 7.5–8.8. These matter after an account takeover, which is the usual route in once a credential is stolen.
  • Mobile Field Service has 11 entries, mostly in the Admin UI. If you don’t use this module, confirm it isn’t deployed and consider whether it should be.
  • CVE-2026-114918 (Concurrent Processing, BI Publisher Integration, 8.7) also addresses CVE-2025-61882, the Clop zero-day. Oracle’s matrix lists it as needing high privileges, which differs from how the 2025 flaw was exploited, so don’t read too much into the scoring. Verify the patch is installed, not just scheduled.
  • BI Publisher has three new items (CVE-2026-114797 and CVE-2026-114789 at 6.1, CVE-2026-114810 at 5.5 in the EBS-XDO component). Most EBS shops run BIP, so include it.

Also check Java. The advisory lists 11 Java SE issues, all remotely exploitable, including server-side API paths. EBS and WebLogic depend on the JDK, so schedule JDK updates with the same release.

SOA and integration deep dive

Integration is the layer most likely to break during patching and the least tested afterward.

EBS Integrated SOA Gateway (ISG). The three new ISG patches (CVE-2026-114903, -114901, -114904) are modest in score. But ISG publishes business logic as web services, and service accounts there are often over-privileged and rarely rotated. After this week’s reports of automated credential harvesting, audit those accounts at the same time as patching.

Service Bus and SOA Suite. Service Bus has an RMI flaw at 9.6 (CVE-2026-91561) and an HTTP flaw at 8.8 (CVE-2026-91566), both needing low privileges. Any proxy service that accepts external partner traffic is a place to look first. SOA Suite and BPM carry third-party component issues (Bouncy Castle, Apache HttpClient, HttpComponents), plus a Human Workflow flaw.

Managed File Transfer. CVE-2026-8763 (9.1, HTTPS, unauthenticated, Bouncy Castle) and CVE-2026-114827 (8.8). If MFT moves payroll, banking or supplier files, this is a data-theft target, which is the Clop playbook.

WebLogic. Several issues are rated 10.0 or 9.8 without authentication. Patch them everywhere, including non-production domains that share credentials or network paths with production.

Regression risk. Patched middleware can change TLS defaults, cipher support, serialization filters and library versions. Build an integration regression pack (one test per partner interface, with message-level assertions) before you patch. Without it, you won’t find out what broke until a partner calls.

The product owner’s view: turn the advisory into a backlog

Treat the CSPU as a product release with business-facing consequences.

1. Map patches to business capabilities, not just components.
Which processes depend on the affected modules? Procure-to-pay (Purchasing, iProcurement, Sourcing), order-to-cash (iStore, Order Management), field operations (Mobile Field Service), and supplier and partner integration (ISG, MFT, Service Bus). Rank capabilities by revenue and regulatory impact. That gives stakeholders a way to approve downtime they can understand.

2. Mind the calendar.
Today is 17 November. Thanksgiving week, Black Friday and Cyber Monday load iStore and order flows. Year-end close is approaching, and many finance teams freeze changes in December. Oracle’s next releases are 15 December 2026 (CSPU) and 19 January 2027 (CPU). A freeze that skips the November patch means carrying it through two more releases. Get the freeze exceptions approved now, not mid-December.

3. Slice the work by risk tier.

TierScopeTarget
0Internet-facing and unauthenticated: EBS 9.8s, iStore, Mobile Field Service, OHS/WebLogic/OAM/OPSS 9.8–10.0, APEX/ORDS 9.8s48–72 hours, or compensating controls with a dated expiry
1Authenticated 7.5+ in EBS and Service Bus, database 9.9s, ISG, MFT, OEM, Java7–10 days
2Remaining medium and low items, third-party components with VEX justificationsNext planned maintenance window

4. Define “done” so it can be audited.
For each Tier-0 item: patch applied in production, version verified by query, integration regression passed, evidence attached to the change ticket, and exposure re-scanned. “Scheduled” doesn’t count.

5. Communicate in business terms.
Executives don’t need CVE numbers. They need: “These patches protect against the data-theft pattern that hit EBS customers in 2025. Here is the downtime and the risk if we defer.”

The chief architect’s view: patch, then reduce what needs patching

Patch cadence alone won’t keep up. These are the structural moves that make the next CSPU less urgent:

  1. Shrink the external surface. Publish only the specific URLs external users need through a reverse proxy or the EBS external-tier and URL-allowlist approach. Block admin UIs, REST and ISG endpoints, and diagnostic paths from the internet. Many of this month’s unauthenticated EBS items sit in paths that most customers don’t need externally.
  2. Segment the stack. The edge, EBS application tier, SOA and WebLogic domains, MFT and the database should have restricted east-west paths. Block T3, IIOP and RMI from anywhere that doesn’t need them.
  3. Control egress. Data-theft extortion needs an exit path. Restrict outbound traffic from application and middleware servers to known destinations, and alert on large transfers from attachment and file stores.
  4. Fix secrets. Move service-account credentials out of config files and repos into a vault, and rotate them on a schedule. Given this week’s automated key-hunting reports, assume exposed secrets will be found.
  5. Control third-party code. For any customer-facing page, inventory every external script, pin versions with Subresource Integrity where possible, and apply a strict Content-Security-Policy. This is the direct lesson from Optimizely.
  6. Secure the patch pipeline. Verify checksums on patch media, restrict who can stage patches, and monitor agent update channels.
  7. Reduce data at rest. Attachments, archived transactions and old supplier records are what extortionists steal. Purge and archive aggressively, and encrypt what remains.
  8. Detect, not just prevent. Log WebLogic, OHS and EBS access, alert on unusual requests to admin and REST paths, and watch for new concurrent-request definitions and unexpected OS-level processes on application servers. You need to be able to answer “did anyone exploit this before we patched?”
  9. Invest in rapid patching. Use online patching, automated pre- and post-checks, and a standing monthly cadence so a critical patch is routine and not a project.

The GRC angle

Auditors will treat this cycle as a control test. Beyond the basics (SLAs, evidence, risk acceptances, supported-version status, earlier Security Alerts for CVE-2026-91403, -114820, -109618 and -109619), add these:

  • Map to your frameworks. Document how the work satisfies vulnerability-management and change-management controls (SOX ITGCs, ISO 27001, NIST CSF, PCI DSS if iStore handles cards). One evidence package can serve several.
  • Track a few KRIs: time to patch Tier-0 items, percent of external endpoints on the allowlist, number of open risk acceptances past expiry, and count of service accounts with stale credentials.
  • Run a “were we hit?” review. For internet-facing EBS and WebLogic, review logs for the period before patching. Patching closes the door but doesn’t tell you whether someone was already inside.
  • Extend vendor-risk management to fourth parties. Optimizely-style incidents show up as “a vendor of my vendor.” Ask critical suppliers how they manage third-party scripts and update channels.
  • Rehearse the extortion scenario. Decide in advance who talks to legal, regulators, insurers and the board if you receive an extortion email, and who decides whether to engage. Don’t write the playbook during the incident.
  • Handle compensating controls honestly. Oracle notes that blocking protocols or removing privileges can break functionality and isn’t a long-term fix. Log each as a time-bound exception with an owner and expiry.
  • Use VEX statements properly. Oracle lists some third-party flaws as non-exploitable (for example, “vulnerable code not in execute path”). Record these as justified exceptions so auditors see a decision, not an omission.

No comments:

Post a Comment

Oracle’s November Patch Storm: What EBS, SOA and WebLogic Teams Must Fix First

  Evidence Pack Share of new patches that are remotely exploitable without authentication Oracle APEX 2 / 2 Java SE 11 / 11 Fusion Middlewar...