[Looking for Charlie's main web site? or all posts?]

Announcing Java Critical Security Update of Nov 17 2026, and "java4shell" - thoughts, resources

If you've not heard, there was a Java update released today (Nov 17, 2026) as what Oracle terms a "critical security patch update" (cspu). It is a ".1" revision for the current long-term support (LTS) releases of Java 25, 21, 17, 11, and 8, as well as the newest short-term release, 27.

Beyond that news, I also have a discussion of the seemingly related "java4shell" vuln. That's been identified as cve-2026-114938, which this update does specifically address. I also share alternative solutions being proposed until that update can be applied.

The new updates are 27.0.1.1, 25.0.5.1, 21.0.13.1, 17.0.21.1, 11.0.33.1, and 1.8.0_513 (aka 8u513) respectively, as revisions to those that were released (without the .1 moniker) on Oct 20. I had blogged about them that day. (And FWIW, I had also indicated in that post how Oracle had announced previously that they were planning such potentially monthly cspu updates--though not necessarily for every product--and that those would be released on the 3rd Tuesday, which is indeed today.)

For some folks, the above is all they need to hear. For others, whether this your first time updating Java or your fiftieth, there are some things that you may or may not know, as I cover here, including links to more info on each of them including what changed, bug fixes (if any), the security fixes each version contains, and more.

Note also that openjdk updates are usually released at the same time or soon after, so the info should also help users of such alternative JDK implementations.

Topics:

Finding more info on these most recent Java updates

As for what changed in the updates, see the release notes for each of: (Again, Java 27 is a "short-term" release while the others are what Oracle calls "long-term support" or LTS releases.)

These Oracle release notes each have a "notes" section indicating a modest change in behavior, and a couple of them have indications of a "fix". Perhaps in time we may see more detail.

More important for this post, they also each end with a pointer to more details on the "fixes for security vulnerabilities", which is the topic of the next section.

Finding more on security matters addressed in these Java updates

As for security fixes included in this update, those are covered for each release by a couple of other Oracle documents.

First, we can find the details (including the 11 CVE's addressed) in the single document listing Java security fixes in this most recent update. That takes you to a section labelled "Oracle Java SE Risk Matrix", which lists each CVE addressed by this update.

Pay close attention to the columns tracked there (for each) as "CVSS VERSION 3.1 RISK" details (score, attack vector, complexity, etc.) See also the "notes" column on the right for each vulnerability, which may temper the severity.

Watch also that many times the listed issues indicate that a vulnerability may be "difficult to exploit" and that many "[do] not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator", which may reduce the concern for you about them depending on your perspective.

Second, see also the Text Form of Risk Matrix for Oracle Java SE, which offers much the same information in a text format, which may be easier to read and/or search.

That said, note as well that while both these documents cover ALL Oracle products, I have linked to the Java-specific sections of the pages. Focus on their references to "Java SE" rather than any specific to GraalVM, which is not the focus of the discussion in this post.

Finally, while I point you to these resources, it's your responsibility to assess that information carefully. And regardless of whether such vulnerabilities may seem to apply to you, generally folks should seek to keep their JVM updated, or at least avoid falling too far behind.

What about today's announced "java4shell", aka cve-2026-114938?

Finally, there is news brewing in the IT world of a new java vuln, labelled "java4shell". It is referred also to as CVE-2026-114938, and though discussed by some resources as being about openjdk, the Oracle docs I just linked to above DO mention that this update addresses that CVE (and others).

It's not quite clear (in these early hours) what the impact of this CVE is, and whether it is a "critical" issue for all users. But it is being discussed in the IT world, and some folks are concerned about it.

Here are a few resources discussing it, in the context of Java and updates:

And each of those points to other resources and are assessing the impact of the Java updates. Watch those spaces for more, but I wanted to at least share this introductory news.

FWIW, both those resources are also pointing out how some researchers are reporting that an alternative solution (for that one "java4shell" issue) may be use of the JVM startup args, "-XX:-UseBASE64Intrinsics, which turns off the Base64 intrinsics, and -XX:UseAVX=2, which turns off all AVX-512 code paths", to negate the vuln being exploited. Again, this is a a very fresh story. I leave you to read up on and follow things as interest warrants. If it becomes "bigger news", we'll all know soon enough.

Oracle's move to monthly security updates (CSPU), which MAY mean Java updates other than quarterly

I'll repeat here what I offered in the Oct CPU update: some folks may not yet have heard that recently Oracle changed their update policy regarding SECURITY updates, where now they plan to follow a new MONTHLY cadence of updates addressing security issues specifically, set to happen on the third Tuesday of the month. That said, it doesn't mean that every Oracle product will GET such a monthly update.

Until today, the first and only one (for Java) was in Aug 2026 (25.0.4.1, 21.0.12.1, 17.0.20.1, and so on). It had its own versions of those bulletins linked to in the previous section. And it was offered on the same download pages I linked to above, though once the new quarterly CPU update had come out it was no longer offered there.

As for anticipating them, Oracle schedules such CSPU updates (potentially released, across all products) to fall on the third Tuesday of each month--not including the month of the release of a CPU update, like this one. So the next such Java CSPU update could be on Dec 15, 2026, or Feb 16 2027 (skipping Jan, when the next CPU update would come out), and so on. You can also see the current "next dates" in both the first security fix list in the previous section as well as a section in the Oracle page on Critical Patch Updates, Critical Security Patch Updates, Security Alerts and Bulletins. But again, it's not a given that there would be a CSPU update *for java* on each of those dates.

Getting notified about Oracle JVM updates

While we're on the topic of knowing when updates of either type may be released, I should point out that you can arrange to get free email notification from Oracle about both kinds of updates (as mentioned and linked to in that previous resource I shared). See the Instructions for subscribing to email notifications of Critical Patch Updates, Critical Security Patch Updates and Security Alerts (which requires having an Oracle account, which again is free). Sadly, the email sent announces updates to any Oracle products: you can't choose to be notified only about updates to Oracle Java products. (One could opt instead to keep an eye out for community discussions of openJDK updates--and some openjdk vendors may offer their own specific notification feature.)

Obtaining the JVM update, from Oracle

As for obtaining downloads of Java updates, again I can report that the updated installers and zips are already available today--even though some of the details about it are not yet available this day of the release (as disucssed above).

You can find all the current versions on this one page. Note that recent Java versions are offered in tabs at the top of the page, while the older LTS versions are offered in tabs further down the page, as I indicate below.

Note that there are also then tabs for the installers of a given update as provided for each supported OS (Linux, macOS, and Windows), and then also both installer binaries and "compressed archives"/zip/tar.gz files.

(Also, to users of Adobe ColdFusion--my primary audience--note that Adobe provides their own downloads page for Oracle Java installer binaries and zips. More on that below, after this next section.)

Oracle downloads for Java 26, 25, and 21

The top of that Oracle downloads page offers the LATEST Java versions, 27 and 25 (the older ones are further down that page):

Note that those updates for Java 25 and above do NOT require a login on the Oracle site, as they are offered under Oracle's NFTC license (explained there). Note that Java 25 will get updates until Sep 2028, a year after the next LTS is expected to be released.

Oracle downloads for Java 21, 17, 11, and 8

As for the remaining versions and their downloads, they are offered further down that Oracle downloads page (or via links I offer next). Note that to download those files you WILL be prompted for an Oracle sign in, as they are offered under a different license (OTN, also discussed there), but note that an Oracle account is available for free if you don't yet have one.

Here are direct links to the section at the bottom for that downloads page for the remaining Java versions:

Obtaining the JVM update, from Adobe

As my blog and work is mostly focused on those using Adobe ColdFusion (as well as Lucee and BoxLang, and all 3 run atop Java), I'll clarify especially for CF users that Adobe offers the Oracle Java downloads, such that one need not log into the Oracle site as discussed in the previous section.

See the CF Downloads page, and its last section offering Java installers ("Java versions supported in ColdFusion"), which includes the installers or zip/archive options, for each of Windows, Linux, and MacOS. FWIW, it offers installers for each of the Java versions supported by each CF product, such as Java 21 for use with CF2025, Java 17 for use with CF2023, Java 11 for use with CF2021 and earlier, and Java 8 for use with the CF API Manager.

As of my posting this today, the Adobe downloads page for CF-related installers does not yet have the downloads for this latest update. Sometime that can take even days. Watch that space for changes over time, or use the Oracle downloads approach I offer above.

Note that until May of 2026, that page had a drop-down you had to use to see its different sections, including one for "java installers". For now, again just scroll down/find the section, "Java versions supported in ColdFusion".

Note also that Adobe tends to offer the 3 most recent updates for the Java versions that are supported for each current CF version (so the 3 most recent Java 21 updates for use with CF2025, the 3 most recent Java 17 updates for use with CF2023, and older java for older software whose downloads they may still offer on that page.) Sometimes they fail to remove older ones, so you may find more than 3 per Java version.

Finally, you may well find the "latest" Java version installers (the current latest update they offer, for each of Java 21, 17, 11, and 8) grouped all together above the other older installers, as I found for the first time with the July 2026 Java updates. For years before, the latest of each was offered above the other older versions of each (all the java 21 versions, with its latest at the top, then all the java 17 versions with its latest version at the top, and so on.) I don't like the vagaries, but I'm just a guide here.

Three technicalities to be aware of, about use of Oracle Java with ColdFusion

While I am speaking to the CF audience here, let me offer 3 points to consider about Oracle licensing matters.

  • As for choosing between these two options of where to obtain these downloads (and given how there can sometimes be a delay in the latest appearing at Adobe), some people assert that CF folks "must use those from the CF downloads page" and not the Oracle one. But I'll note that every time I've done a binary compare of the installers files (of some given version and OS, on the day it came out and Adobe offered it), the ones Adobe offers have been identical to those offered on the Oracle site (at least for the identical build number, which may change slightly over time on the Oracle site though not the Adobe site). As this installer includes the Java license, I can't see how anyone could assert that it matters WHERE you get an identical installer. But IANAL. The choice is yours, if you want the update ASAP and Adobe doesn't offer it yet.
  • While some may be tempted to go get some other JVM/JDK, like an openjdk, note that Adobe has always formally supported only the use of Oracle Java with CF, not other OpenJDK implementations. I'm not saying it WON'T work. But be aware of this point--and please consider pointing out when you may be using some non-Oracle JVM when reporting issue with CF.
  • Finally, note also that Adobe licenses Oracle Java for our use of it with CF--but CF only. More on that in the resource discussed next. This applies whether the version is offered by Oracle under its OTN or NFTC license--though again only for your use of Java with CF.

Other topics you may be interested to know, and where I discuss them

Some readers may find the above so far to have been "a lot to consider" already, but there is indeed far more that you could and should consider before applying a Java update. And for a few years, I would cover such additional topics within this sort of blog post, each time I announced the new JVM update. But I've decided recently to split that off into its own blog entry, and I will point to that instead in each of these such JVM update announcement posts, in order to keep this relatively "brief". (I've kept some of the other points above because they affect OBTAINING the download.)

In that other post, I address such issues as:

  • Obtaining and learning still more about available JVM updates
  • What about other JVM distributions besides Oracle?
  • News for my CF audience: Oracle licensing, obtaining updates from Adobe, and more
  • Should you apply the update? how soon?

Then I cover a few things that you should be aware of if skipping over previous JVM updates (Sometimes people are literally a couple to a few years behind):

Again, that other post of mine with more info is here: Several things to consider when applying JVM updates.

Wrapping up, getting more help

I hope all that may be helpful for you.

Feel free to ask questions or raise comments below, or for direct help note that I offer remote screenshare consulting help, where I am usually able to quickly fix problems (that might take me only minutes to resolve, but might take many folks hours on their own--if they don't deal with these issues daily like I do in helping people).


For more content like this from Charlie Arehart: Need more help with problems?
  • If you may prefer direct help, rather than digging around here/elsewhere or via comments, he can help via his online consulting services
  • See that page for more on how he can help a) over the web, safely and securely, b) usually very quickly, c) teaching you along the way, and d) with satisfaction guaranteed
Comments
Copyright ©2026 Charlie Arehart
Carehart Logo
BlogCFC was created by Raymond Camden. This blog is running version 5.005.
(Want to validate the HTML in this page?)

Managed Hosting Services provided by
xByte cloud Hosting