Summary
- Oracle's October 2026 Critical Patch Update is publicly readable: it prints 1295 new security patches, the affected product families and a version-level rule for who may receive them.
- Oracle's own programme pages state that the patches "are available to customers with valid support contracts," and the third support stage, Sustaining Support, prints an explicit exclusion covering critical patch updates while staying available indefinitely.
- The operative boundary is a dated table read release by release rather than the policy's general five-year sentence: Oracle Database 19c prints Premier Support running to December 2029, and 21c prints "Not Available" in the Extended Support column.
A warning addressed to everyone
Start with what is unconditional, because it is more than the genre usually offers. The security-alerts index, read in its European edition, defines a Critical Patch Update as "a collection of patches for multiple security vulnerabilities," notes that the patches "are usually cumulative," and prints a cadence anyone can plan around: the third Tuesday of January, April, July and October, with the next four dates given as 19 January 2027, 20 April 2027, 20 July 2027 and 19 October 2027. I checked all four against a calendar; each really is the third Tuesday of its month.
The same index keeps score of its own corrections. It lists "Critical Patch Update - October 2026 | Rev 3, 4 November 2026" and "Critical Patch Update - July 2026 | Rev 7, 20 August 2026." Run the page's own cadence backwards and the October release falls on 20 October, the July release on 21 July. That is fifteen days from release to third revision in one case and thirty days to seventh revision in the other — my subtraction, not a printed figure. It is also the clearest sign that this is a living document rather than a one-shot notice, and that the vendor keeps amending what it told you.
A second stream has since appeared beside it: Critical Security Patch Updates, listed from 28 May 2026 and described under the same contract condition. Whatever else is moving, the patch programme is not contracting. The October 2026 advisory carries the familiar urgency verbatim — "Due to the threat posed by a successful attack, Oracle strongly recommends that customers apply Critical Patch Update security patches as soon as possible" — and then hands the reader over to a Patch Availability Document column rather than to a file.
The sentence that decides who can install
Here is the whole gate, in three pieces, each printed by the publisher.
First, the index, in the very paragraph that defines the programme: "They are available to customers with valid support contracts." Not "customers in good standing." Not "licensed users." A contract.
Second, the programme FAQ, whose own last-updated line reads 27 May 2026, narrows the version scope: "only releases in these first two stages of support are included in the Critical Patch Update, Critical Security Patch Update, and Security Alert program." The FAQ is naming Premier and Extended Support, the first two stages of the Lifetime Support Policy.
Third, the policy document itself — Oracle's Lifetime Support Policy for Technology Products, document 069183, printed with an effective date of 13 November 2026 — names what each stage delivers. Premier Support includes, in its own words, "Updates, fixes, security alerts, data fixes, and critical patch updates." Extended Support "provides you with an extra three years of support for specific Oracle releases for an additional fee."
And then the third stage, Sustaining Support, available "for as long as you license your Oracle products," prints its exclusion in a line that does not need commentary: "Sustaining Support does not include: New updates, fixes, security alerts, data fixes, and critical patch updates." What it does carry is narrower and carries its own conditions — "Fixes, updates, and critical patch updates created during Premier Support and Extended Support (if offered and only after the Extended Support period ends)." Read the qualifiers: if offered, and only after the Extended period ends.
Nothing new is created for a release once it is Sustaining. An operator there can still open a service request; the stream of new security fixes has stopped at the door.
The counterweights, before the finding
Four honest weights belong on the other side of the scale, and each is printed by Oracle.
The advisory detail itself is unconditional. Count, product families, version eligibility, the recommendation to patch — all of it sits on the open web, and the version gate is disclosed rather than buried. Many vendors will not tell you which of their releases you are no longer allowed to fix.
The patches "are usually cumulative," which is a real operational mercy: apply the current bundle and you are not left assembling three years of intermediate builds.
The FAQ says the quiet part plainly: "It is not mandatory to install Critical Patch Updates, Critical Security Patch Updates, or Security Alerts, but Oracle strongly recommends that they are applied." This is maintenance advice, not conscription.
And the calendar is not uniformly stingy. The general sentence says Premier Support runs "five years from their general availability date." The table does not always obey that sentence, and where it disobeys it tends to be generous — as the next section shows.
The perimeter is a row, not a sentence
The policy prints its Oracle Database releases in a dated table, and that table, not the five-year sentence, is where the real boundary lives.
Read the rows as printed: 11.2, general availability September 2009, Premier Support to January 2015, Extended Support to December 2020, Sustaining indefinitely. 19c, a Long Term Support Release, general availability 4 April 2019, Premier Support to December 2029, Extended Support to December 2032, Sustaining indefinitely. 21c, an Innovation Release, general availability August 2021, Premier Support to July 2027, Extended Support "Not Available," Sustaining indefinitely. 26ai, general availability October 2025, Premier Support to December 2031, Extended Support "TBD," Sustaining indefinitely.
Two spans in that table are worth putting on their own measurement stage, and both figures below are mine.
Take 19c. From its printed general availability of 4 April 2019 to a Premier Support cell reading December 2029 is ten years, eight months and 27 days if the month is read at its last day, or ten years, seven months and 27 days if read at its first. Against the policy's own general sentence — five years from general availability, which lands on 4 April 2024 — the printed row extends Premier Support by five years, eight months and 27 days beyond the rule that supposedly defines it. The row wins. It always wins; the general sentence is a summary and the row is the commitment.
Take 21c. From August 2021 to a Premier Support cell reading July 2027 is five years and eleven months. The Extended Support column reads "Not Available," so for this release there is no paid extra period at all: when Premier closes, the critical patch stream closes with it, and Sustaining is what remains.
A second Oracle document, the Coverage for Technology chart, corroborates the 19c row exactly — "19c (Long Term Support Release) | 4 Apr 2019 | Dec 2029 | Dec 2032 | Indefinite" — which matters, because a stranger hunting for a typo should find two documents saying the same thing and no easy exit.
The chart also shows how fine the perimeter can get. Its footnote, dated to the day, carves a named component out of the middle of the paid tiers: "during the Premier Support period of May 1, 2027 through December 31, 2029, and the Extended Support period from January 1, 2030 through December 31, 2032, support will be excluded for Java 8 related third-party software," adding that Oracle Database 19c "will no longer receive updates for Java after" December 2030. A customer can be squarely inside Premier Support, paying for it, and still find one dependency outside the line on a printed date. That is not a scandal.
It is what a document looks like when it means what it says, and it is the reason the table has to be read rather than summarised.
What the six pages do not join
Across the six pages read on 22 November 2026 — the index, the October 2026 advisory, the FAQ, the support landing page and the two policy documents — no sentence names both a specific Critical Patch Update advisory and a support tier. Nothing states what remedy an operator can obtain for a release that has left Premier and Extended Support.
Nothing prints the price of Extended Support; the policy says only that it is available "for an additional fee." And nothing carries a direct public link to a patch file: the advisory routes retrieval through "links in the Patch Availability Document column" and holds its executive summary in a My Oracle Support note.
Those are findings about six pages read on one day, and they say nothing about pages outside them. Nor do they support any claim that a fix was withheld, delayed or misdescribed. The documents reviewed do not allege misconduct and this article does not either. What they show is a division of labour: one office writes the warning, another writes the calendar, and the reader is left to perform the join.
Oracle Corporation's own published record does perform the join in one direction only. Every reader learns that 1295 new security patches exist. Only a reader who then opens a separate policy document, on a different part of the site, learns whether their installation is allowed to receive them.
The field Oracle already writes
There is a cheap, checkable fix available, and it does not require Oracle to give anything away. It requires one sentence in a document the company already publishes and dates.
The Sustaining Support definition currently excludes new security fixes. Amend it to include new fixes and critical patch updates for publicly disclosed vulnerabilities, and the safety path survives the commercial boundary. The customer still pays for upgrades, features, certifications and the rest of what tiers sell. What stops being for sale is the answer to a flaw the vendor itself just published to the world.
Until then, the practical rule for anyone running Oracle software is unglamorous: find your release in the dated table, read the cell that ends Premier Support, and treat that date as the last day of the security relationship, not the first day of a negotiation. Thirty days of revision lag, a stream of new patches every quarter and a policy document dated 13 November 2026 all point the same way. The flaw was published for free. The perimeter that decides whether you can install its repair was published too — in a different document, with a different author, a month later. Oracle Corporation's directory entry records the entity behind both.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






