Oracle now runs two patch streams, and October’s quarterly update alone carries 1,283 fixes
Oracle's October Critical Patch Update lands alongside a monthly stream it began in May. Organisations that built change calendars around four Oracle dates a year are now managing about ten, and the streams do not substitute for one another.

Oracle released its October 2026 Critical Patch Update on 20 October with 1,283 new security patches [1][2]. The number is not the finding. The finding is that this quarterly release now sits inside a second, monthly cadence that Oracle began in May, and that the two are published separately, counted separately and scheduled on different dates. A change calendar built around four Oracle advisories a year no longer describes what Oracle ships.
What the release contains
The pre-release announcement, which Oracle notes may change before the full advisory is published, breaks the 1,283 patches down by product family [1]. Three families carry an entry at the maximum CVSS 3.1 score of 10.0: E-Business Suite with 196 patches, Fusion Middleware with 196, and JD Edwards with 102 [1]. The concentration of unauthenticated network exposure is uneven and worth reading closely.
- Fusion Middleware: 196 patches, 132 of them flagged as potentially remotely exploitable without authentication, highest CVSS 10.0. The family includes Access Manager, Identity Manager, HTTP Server and WebLogic Server [1][10].
- E-Business Suite: 196 patches, 34 remotely exploitable without authentication, highest CVSS 10.0 [1].
- Communications: 124 patches, 87 remotely exploitable without authentication, highest 9.8 [1].
- Siebel CRM: 123 patches, 67 remotely exploitable without authentication, highest 9.9 [1].
- PeopleSoft: 109 patches, 41 remotely exploitable without authentication, highest 9.8 [1].
- JD Edwards: 102 patches, 44 remotely exploitable without authentication, highest 10.0 [1].
- MySQL: 98 patches, 29 remotely exploitable without authentication, highest 9.8 [1]. Java SE: 55 patches, 49 remotely exploitable without authentication [1].
- Database Server, by contrast: 13 patches, 3 remotely exploitable without authentication, highest 8.8 [1].
Summing Oracle’s per-family figures gives roughly 598 patches for flaws reachable over a network without credentials. Oracle does not publish that total, and it is the desk’s arithmetic rather than a vendor statement. It is still the number that matters for triage, because it is the subset an attacker can reach without a foothold.
The cadence change is the operational story
Oracle published its first Critical Security Patch Update on 28 May 2026 [3]. Further releases followed in June, August and September, and Oracle has announced them for 17 November and 15 December 2026, then 16 February and 16 March 2027 [3]. Quarterly Critical Patch Updates continue on their own schedule, announced for 19 January, 20 April, 20 July and 19 October 2027 [3]. Counting both streams, 2026 has produced eight Oracle security releases to October with two more scheduled.
Volumes across those releases vary by a factor of four. The January 2026 Critical Patch Update contained 337 patches [7], April contained 481 [6], July contained 1,448 [5] and October contains 1,283 [1]. The September Critical Security Patch Update contained 673 [4]. July, not October, is the largest single release of the year.
Oracle describes the relationship between the two streams in more than one way, and the difference is not cosmetic. The security alerts index states that Critical Security Patch Updates are targeted, high-priority fixes in a smaller format that complement the quarterly cumulative updates [3]. The September advisory repeats that framing [4]. Oracle’s own blog post accompanying the October release urges customers to move to a monthly patching cycle, starting with the October updates [2]. Trade analysis of the September release described Oracle as having accelerated its patching rhythm from quarterly to monthly [9]. The reading that survives all three is that both streams continue and neither is optional.
Oracle’s September advisory makes the consequence explicit for anyone who has fallen behind: an organisation that skipped earlier releases should review previous Critical Security Patch Updates and quarterly Critical Patch Updates rather than assume the newest release covers the backlog [9]. The quarterly updates are cumulative; the monthly ones are not a superset of them.
Figures that differ between sources
- The September release is given as 673 new patches by Oracle [4] and by three independent analyses [8][9][11]. One of those analyses counts 672 unique CVE identifiers in the risk matrices and estimates an effective total past 800 once bundled patches are included, and labels that an estimate of its own rather than an Oracle figure [11].
- Severity breakdowns for September differ in vocabulary. One analysis gives 104 critical, 503 important and 59 medium [8]; another states only that more than 100 were critical [11].
- Totals for remotely exploitable unauthenticated flaws in September are given as over 240 in one analysis [11] and are not stated as a total by Oracle [4]. Per-family figures are consistent across sources.
Exploitation is not hypothetical
Oracle’s advisories carry a standing statement that it periodically receives reports of attempts to exploit vulnerabilities for which patches already exist, and that some of those attempts succeeded against customers who had not applied the available patches [4][5]. Two 2026 cases give that statement specific weight.
CVE-2026-46817, rated CVSS 9.8, affects E-Business Suite 12.2.3 through 12.2.15 and allows an unauthenticated attacker to take over the Oracle Payments component over HTTP [12]. A threat intelligence firm first reported exploitation on 27 June 2026, describing six unauthenticated file-read attempts from a single European address as a targeted proof-of-concept rather than broad scanning, at a point when no public proof-of-concept existed [12]. Reporting on 17 July placed it in the US exploited-vulnerability catalogue with a three-day federal remediation deadline of 18 July under a binding operational directive [12]. Separately, CVE-2026-21962, an improper access control flaw in Oracle HTTP Server and the WebLogic Server Proxy Plug-in, was reported as added to the same catalogue on 24 August 2026 [13]. Both listing dates are cited from secondary reporting, as the catalogue could not be retrieved directly.
Both are unauthenticated, network-reachable components. That is the same profile as the largest blocks in the October release, and it is the argument for ordering the queue by exposure rather than by score.
Building the queue
- Inventory by product, version, owner and internet exposure, including Oracle components embedded inside third-party applications. Ask those vendors which Oracle components they ship and when fixes will reach their builds [10].
- Order by exposure first. Internet-facing systems and unauthenticated remote-exposure paths, particularly login, API and integration endpoints, go ahead of internal systems with higher scores [10].
- Split the work by owner into separate queues for databases, middleware, identity, Java, analytics and packaged applications rather than raising one generic change ticket [10].
- Confirm the support phase before planning. Patches cover only releases under Premier or Extended Support, and releases outside those phases were not tested against these vulnerabilities [5][9].
- Put both streams in the change calendar using Oracle’s published dates [3], and treat the monthly release as a scheduled event rather than an exception.
- Capture configuration, account and log baselines before patching so unexplained changes afterwards are visible [10].
- Where a fix is delayed, test interim controls before relying on them. Blocking required network protocols or removing privileges can break functionality and is not a long-term substitute [9].
For organisations in Malaysia and the wider region, the practical friction is scheduling. E-Business Suite, PeopleSoft, Siebel and Fusion Middleware are concentrated in regional shared service centres, where change freezes cluster around financial close and public holidays. A monthly cadence collides with that calendar in a way a quarterly one did not, and the collision is foreseeable rather than sudden.
What this changes for offensive-security work
Patch volume is a poor measure of risk and a worse measure of progress. The useful metric is time-to-remediation on the internet-facing, unauthenticated subset, which in October is a few hundred patches rather than 1,283. Both Oracle vulnerabilities confirmed as exploited this year sat in that subset. Testing programmes should reflect it: external attack surface discovery against Oracle components, including those embedded in supplier software, and verification that the monthly stream is actually being consumed rather than deferred until the next quarterly release.
Sources
Every R3KONX article cites its primary material. 13 sources, in order of first citation. Links open the original publication.
- Oracle Critical Patch Update Advisory - October 2026 (pre-release announcement) Oracle · 2026-10-20
- October 2026 Critical Patch Update Released Oracle Security Blog · 2026-10-20
- Critical Patch Updates, Critical Security Patch Updates, Security Alerts and Bulletins Oracle · accessed 2026-10-21
- Oracle Critical Security Patch Update Advisory - September 2026 Oracle · 2026-09-15
- Oracle Critical Patch Update Advisory - July 2026 Oracle · 2026-08-20
- Oracle Critical Patch Update Advisory - April 2026 Oracle · 2026-04-24
- Oracle Critical Patch Update Advisory - January 2026 Oracle · 2026-02-02
- Oracle Critical Security Patch Update, September 2026 Review Qualys Threat Research Unit · 2026-09-16
- Oracle's September patches put Fusion Middleware back in the hot seat CSO Online · 2026-09-16
- Oracle October 2026 CPU: Build the Patch Queue Before October 20 about InfoSec · 2026-10-19
- Oracle Critical Security Update - 673 Vulnerabilities Patched Across Product Families Cyber Security News · 2026-09-16
- Critical Oracle EBS bug added to CISA list of exploited vulnerabilities SC Media · 2026-07-17
- CISA Adds Oracle HTTP Server Vulnerability to KEV Catalog CyberNetSec.io · 2026-08-24
Researched and written by the R3KONX analysis desk from the cited primary material. The October 2026 figures are taken from Oracle's pre-release announcement, which states that its information may change before publication of the full advisory; the total of remotely exploitable unauthenticated flaws is the desk's sum of Oracle's per-family figures and is not a figure Oracle states. Catalogue listing dates for the two exploited Oracle vulnerabilities are cited from secondary reporting because the catalogue itself could not be retrieved. Corrections to event@r3konx.asia.
