<?xml version="1.0" encoding="utf-8"?>
			<?xml-stylesheet type="text/css" href="https://www.carehart.org/blog/client/rss.css" ?>
			
			<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
			<channel>
			<title>Charlie Arehart - Server Troubleshooting - cf2023</title>
			<link>https://www.carehart.org/blog/client/index.cfm</link>
			<atom:link href="https://www.carehart.org/blog/client/rss.cfm" rel="self" type="application/rss+xml" />
			<description>Charlie Arehart - Server Troubleshooting</description>
			<language>en-us</language>
			<lastBuildDate>Tue, 08 Sep 2026 23:52:00 -0500</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>blogmaster@carehart.org (Charlie Arehart)</managingEditor>
			<webMaster>blogmaster@carehart.org (Charlie Arehart)</webMaster>
			
			<item>
				<title>Announcing ColdFusion updates of Sep 8 2026 - p1 security update</title>
				<link>https://www.carehart.org/blog/2026/9/8/coldfusion_updates_released_sep_8_2026</link>
				<description>
				
				Adobe has released another set of updates today, Sept 8 2026, for CF2025 (update 13) and CF2023 (update 24). As with other recent updates, these &quot;&lt;i&gt;resolve critical, important, and moderate vulnerabilities that could lead to arbitrary code execution, arbitrary file system read, privilege escalation, security feature bypass, and memory exposure.&lt;/i&gt;&quot;  [More]
				</description>
				
				<category>updates</category>
				
				<category>security</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<pubDate>Tue, 08 Sep 2026 23:52:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2026/9/8/coldfusion_updates_released_sep_8_2026</guid>
				
			</item>
			
			<item>
				<title>Announcing ColdFusion updates of Aug 11 2026 - p1 security update - thoughts and resources</title>
				<link>https://www.carehart.org/blog/2026/8/12/coldfusion_updates_released_aug_11_2026</link>
				<description>
				
				An update for ColdFusion has been released, Aug 11 2026, for each of CF2025 (as its update 12) and CF2023 (as its update 23).

Read on for more, including details and observations I offer about what else has changed with this update, as well as concluding thoughts on best practices regarding any CF update.  [More]
				</description>
				
				<category>updates</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<pubDate>Wed, 12 Aug 2026 01:20:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2026/8/12/coldfusion_updates_released_aug_11_2026</guid>
				
			</item>
			
			<item>
				<title>Announcing ColdFusion updates of Jul 14 2026 - p1 security update -  thoughts and resources</title>
				<link>https://www.carehart.org/blog/2026/7/15/coldfusion_updates_released_jul_14_2026</link>
				<description>
				
				An update for ColdFusion has been released, July 14 2026, for each of CF2025 (as its update 11) and CF2023 (as its update 22).

In brief, this update &lt;b&gt;is another classed by Adobe as a P1 (Priority 1, &quot;Critical&quot;) security update&lt;/b&gt;.&#xa0; Specifically, the Adobe produce security bulletin (linked to below) indicates that the update addresses &quot;vulnerabilities that could lead to arbitrary code execution, privilege escalation, arbitrary file system read, and security feature bypass&quot;. And while it also says that, &quot;Adobe is not aware of any exploits in the wild for any of the issues addressed in these updates&quot;, note that it&apos;s not uncommon that &lt;b&gt;the vulns will immediately be being reverse-engineered and exploited&lt;/b&gt; by bad guys--or good guys trying to warn folks.

As such, it&apos;s always important to apply CF updates, and still more important for CF security updates, but then especially if they are classed as &quot;critical&quot; like this (though it&apos;s also true that some vulns are in features that may be disabled by default, or disabled for you, in which case their urgency is diminished).

Finally, as happens with about 30% of CF security updates, this one has a potential breaking change (which could affect some apps but not all), and &lt;b&gt;there is a new jvm flags/args which would allow you to trade back that improved security for compatibility&lt;/b&gt;. You should consider such changes carefully &lt;b&gt;before just applying the update in prod&lt;/b&gt; (as some do) or relying on only light testing of a few pages. The same care should be taken before &lt;b&gt;just blithely sticking the jvm args in for compatibility sake&lt;/b&gt;.

Forewarned is forearmed. Read on for more, including many other observations I offer about what else has changed with this update, and some concluding thoughts on best practices regarding any CF update.  [More]
				</description>
				
				<category>updates</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<category>PMT</category>
				
				<pubDate>Wed, 15 Jul 2026 15:16:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2026/7/15/coldfusion_updates_released_jul_14_2026</guid>
				
			</item>
			
			<item>
				<title>Announcing ColdFusion updates of Jun 30 2026 - p1 security update -  thoughts and resources</title>
				<link>https://www.carehart.org/blog/2026/6/30/coldfusion_updates_released_jun_30_2026</link>
				<description>
				
				An update for ColdFusion has been released, June 30 2026, for each of CF2025 (as its update 10) and CF2023 (as its update 21).

In brief, this update &lt;b&gt;is classed by Adobe as a P1 (Priority 1, &quot;Critical&quot;) security update&lt;/b&gt;. Then again, the security bulletin (link below) indicates as of today that, &quot;Adobe is not aware of any exploits in the wild for any of the issues addressed in these updates.&quot;  Even so, &lt;b&gt;in the days after there have here have been public announcements of one or more of the vulns being reverse-engineered and exploited&lt;/b&gt;, as I discuss &lt;a href=&quot;#exploits&quot;&gt;below&lt;/a&gt;. 

Even so, as happens with about 30% of CF security updates, this one has potential breaking changes (which could affect some apps but not all), and &lt;b&gt;there are also new jvm flags/args which would allow you to trade back that improved security for compatibility&lt;/b&gt;. You should consider such changes carefully &lt;b&gt;before just applying the update in prod&lt;/b&gt; (as some do) or relying on only light testing of a few pages. The same care should be taken before &lt;b&gt;just blithely sticking the jvm args in for compatibility sake&lt;/b&gt;. 

Forewarned is forearmed. Read on for more, including many other observations I offer about what else has changed with this update, and some concluding thoughts on best practices regarding any CF update.  [More]
				</description>
				
				<category>updates</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<pubDate>Tue, 30 Jun 2026 20:57:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2026/6/30/coldfusion_updates_released_jun_30_2026</guid>
				
			</item>
			
			<item>
				<title>Announcing ColdFusion updates of Jun 9 2026 - p1 security update -  thoughts and resources</title>
				<link>https://www.carehart.org/blog/2026/6/9/coldfusion_updates_released_jun_9_2026</link>
				<description>
				
				An update for ColdFusion has been released, June 9 2026, for each of CF2025 (as its update 9) and CF2023 (as its update 20).  

In brief, this update &lt;b&gt;is classed by Adobe as a P1 (Priority 1, &quot;Critical&quot;) security update&lt;/b&gt;. Then again, the security bulletin (link below) indicates as of today that, &quot;Adobe is not aware of any exploits in the wild for any of the issues addressed in these updates.&quot;

The update also includes a still-more recent update to the version of Tomcat embedded within each CF version than previous CF updates. To be clear, there are no other changes, bug fixes, or known issues indicated for this update.

FWIW, some may know that Adobe released an update just last month--which was ONLY for CF2025, as &lt;a href=&quot;https://www.carehart.org/blog/2026/5/20/major_coldfusion2025_update_released_may_20_2026&quot;&gt;I discussed in a post that day, May 20&lt;/a&gt;. That DID include many new features and changes (including changed behaviors), so note that if you are on CF2025 and are skipping from update 7 or earlier, look to that post for more before proceeding.

And like with each CF update, I share the details about the update (from Adobe and from others) as well as additional info you may want to consider before (or after) doing the update.

Read on for more, including many other observations I offer about what else has changed with this update, and some concluding thoughts on best practices regarding any CF update.  [More]
				</description>
				
				<category>updates</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<pubDate>Tue, 09 Jun 2026 21:50:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2026/6/9/coldfusion_updates_released_jun_9_2026</guid>
				
			</item>
			
			<item>
				<title>Announcing ColdFusion updates of Apr 14 2026 - p1 security update -  thoughts and resources</title>
				<link>https://www.carehart.org/blog/2026/4/14/coldfusion_updates_released_apr_14_2026</link>
				<description>
				
				An update for ColdFusion has been released, Apr 14 2026, for each of cf2025 (as its update 7) and cf2023 (as its update 19).  In brief, this update &lt;b&gt;is classed by Adobe as a P1 (Priority 1, &quot;Critical&quot;) security update&lt;/b&gt;. Then again, the security bulletin (link below) indicates as of today that, &quot;Adobe is not aware of any exploits in the wild for any of the issues addressed in these updates.&quot;

(This is the second update since CF2021 has reached its end of life &lt;a href=&quot;https://www.carehart.org/blog/2025/11/7/cf2021_endoflife_nov_10&quot;&gt;as I blogged previously&lt;/a&gt;, which is something folks running that should beware. You are now QUITE exposed to things fixed in these two updates, for which there is no fix for you.)

In this post, I share the details about the update (from Adobe and from others). I also share additional info you may want to consider before (or after) doing the update.

Read on for more, including many other observations I offer about what else has changed with this update, and some concluding thoughts on best practices regarding any CF update.  [More]
				</description>
				
				<category>updates</category>
				
				<category>security</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<pubDate>Tue, 14 Apr 2026 22:14:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2026/4/14/coldfusion_updates_released_apr_14_2026</guid>
				
			</item>
			
			<item>
				<title>Announcing ColdFusion updates of Jan 13 2026 - p1 security update - thoughts and resources</title>
				<link>https://www.carehart.org/blog/2026/1/14/coldfusion_updates_released_jan_13_2026</link>
				<description>
				
				An update for ColdFusion has been released, Jan 13 2026, for each of cf2025 (as its update 6) and cf2023 (as its update 18). (This is the first update since CF2021 has reached&#xa0; its end of life &lt;a href=&quot;https://www.carehart.org/blog/2025/11/7/cf2021_endoflife_nov_10&quot;&gt;as I blogged previously&lt;/a&gt;, so this is the first cf update NOT available for cf2021, which is something folks running that should beware.)

In brief, this update (for both versions) &lt;b&gt;addresses a P1 (Priority 1, &quot;Critical&quot;) security vulnerability&lt;/b&gt;, related to the Apache Tika java framework which Adobe embeds for certain processing with CF.

Before proceeding, &lt;b&gt;it&apos;s of some concern to note&lt;/b&gt; that unlike recent CF security updates, Adobe does NOT report (in the APSB, linked to below) that they are, &quot;not aware of any exploits in the wild for any of the issues addressed in these updates.&quot; That omission
&lt;b&gt;would seem to imply that they ARE aware of this vuln being exploited&lt;/b&gt;, which raises the urgency of getting it applied. (It also raises the concern all the more for those on CF2021 or earlier, for whom Adobe will no longer offers ANY updates, including security updates.) 

In this post, I share the details about the update (from Adobe and from others). I also share additional info you may want to consider before (or after) doing the update.

Read on for more, including many other observations I offer about what else has changed with this update, and some concluding thoughts on best practices regarding any CF update.  [More]
				</description>
				
				<category>updates</category>
				
				<category>security</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<pubDate>Wed, 14 Jan 2026 00:21:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2026/1/14/coldfusion_updates_released_jan_13_2026</guid>
				
			</item>
			
			<item>
				<title>One explanation and solution for when applying CF updates uninstalls new packages unexpectedly</title>
				<link>https://www.carehart.org/blog/2025/12/10/applying_cf_updates_may_uninstall_packages_unexpectedly</link>
				<description>
				
				I offer in this post a solution to a problem that I and others experienced regarding the latest CF update (released Dec 10, 2025 for ColdFusion 2025, 2023, and 2021, which &lt;a href=&quot;https://www.carehart.org/blog/2025/12/10/Announcing-ColdFusion-updates-released-Dec-9-2025--p1-security-update-and-more&quot;&gt;I just blogged about&lt;/a&gt; separately).

We only experienced it with CF2023, but &lt;b&gt;others have reported the problem in the past, with various CF updates to any CF version&lt;/b&gt;. As I&apos;ll explain it seems to be a caching problem relative to Adobe&apos;s servers (so some people may experience it, but not others):

&lt;ul&gt;
&lt;li&gt;First, &lt;u&gt;you may find that after applying the update all the of the packages that were to be updated by the release will instead be UNINSTALLED unexpectedly/&lt;/u&gt;&lt;/li&gt;
&lt;li&gt;Even worse, that could mean that &lt;u&gt;the administrator package is uninstalled, such that you can&apos;t get to the CF Admin after the update&lt;/u&gt;...which will also mean you can&apos;t use the admin to try to &quot;uninstall the update&quot; (if you wanted to).&lt;/li&gt;
&lt;/ul&gt;

Of course, you could go the command line route, as you would be told to consider doing if the Administrator package was uninstalled, using CF&apos;s cfpm tool to either install the admin package or even perhaps try to uninstall the update entirely.

&lt;u&gt;But I have what seems to be a better solution.&lt;/u&gt; It&apos;s quite simple, but bear with me while I explain it...both to help you (and Adobe) better understand what seems amiss, and in case more info may come out soon from them or other folks.

&lt;b&gt;Beware also that if you may have &quot;solved the problem&quot; yourself, consider what I have to say below--you should confirm that you DO in fact have the correctly UPDATED packages, which you may have installed using that cfpm tool.&lt;/b&gt;  [More]
				</description>
				
				<category>updates</category>
				
				<category>cf2021</category>
				
				<category>cf2025</category>
				
				<category>troubleshooting</category>
				
				<category>cf2023</category>
				
				<pubDate>Wed, 10 Dec 2025 05:06:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2025/12/10/applying_cf_updates_may_uninstall_packages_unexpectedly</guid>
				
			</item>
			
			<item>
				<title>Announcing ColdFusion updates of Dec 9 2025 - p1 security update and more</title>
				<link>https://www.carehart.org/blog/2025/12/10/Announcing-ColdFusion-updates-released-Dec-9-2025--p1-security-update-and-more</link>
				<description>
				
				An update for ColdFusion has been released, Dec 9 2025, for each of cf2025 (update 5), cf2023 (update 17) and cf2021 (update 23). This is in fact that FINAL update of CF2021, as it has reached its end of life &lt;a href=&quot;https://www.carehart.org/blog/2025/11/7/cf2021_endoflife_nov_10&quot;&gt;as I blogged last month&lt;/a&gt;.

In brief, this update (for all 3 versions) &lt;b&gt;addresses several P1 (Priority 1, &quot;Critical&quot;) security vulnerabilities&lt;/b&gt;, and also updates Tomcat, along with updating several CF packages, and makes some other changes (see below). Note that Adobe is also reporting currently that, &quot;&lt;i&gt;Adobe is not aware of any exploits in the wild for any of the issues addressed in these updates.&lt;/i&gt;&quot;

In this post, I share the details about the update (from Adobe and from others). I also share additional info you may want to consider before (or after) doing the update.&#xa0;

Having installed the update for each of the releases on multiple machines, I can report that it went well expect for this:
&lt;blockquote&gt;
&lt;strong&gt;Warning: beware that some folks implementing the update for CF2023 the first day (myself included) found that after applying the update, the CF Admin was inaccessible and packages that were updates were unexpectedly uninstalled.&lt;/strong&gt; I have offered a follow-up blog post on that, &lt;a href=&quot;https://www.carehart.org/blog/2025/12/10/applying_cf_updates_may_uninstall_packages_unexpectedly&quot;&gt;One explanation and solution for when applying CF updates uninstalls new packages unexpectedly&lt;/a&gt;, including how to solve the problem as I see it, and how to ensure your own manual efforts to solve it are complete.
&lt;/blockquote&gt;

Read on for more, including many other observations I offer about what else has changed with this update, and some concluding thoughts on best practices regarding any CF update.  [More]
				</description>
				
				<category>updates</category>
				
				<category>cf2021</category>
				
				<category>security</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<pubDate>Wed, 10 Dec 2025 02:40:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2025/12/10/Announcing-ColdFusion-updates-released-Dec-9-2025--p1-security-update-and-more</guid>
				
			</item>
			
			<item>
				<title>Announcing ColdFusion updates of Sep 9 2025 - p1 security update -  thoughts and resources</title>
				<link>https://www.carehart.org/blog/2025/9/9/coldfusion_updates_released_sep_9_2025</link>
				<description>
				
				An update for ColdFusion has been released, Sep 9 2025, for each of cf2025 (update 4), cf2023 (update 16) and cf2021 (update 22).  In brief, it &lt;b&gt;addresses a single P1 (Priority 1, &quot;Critical&quot;) security vulnerabilities&lt;/b&gt;, along with an indicated update to the &quot;feed&quot; package (used by cffeed). Note that Adobe is also reporting currently that, &quot;Adobe is not aware of any exploits in the wild for any of the issues addressed in these updates.&quot; More below.

As usual, there are a number of things you should consider before (or after) doing the update, with some discussed in Adobe&apos;s resources on the update (there are more than one), and some info that I share below based on my experience helping people apply this and past updates. 

In this post, I share the details about the update (from Adobe and from others). I can report I have installed the update for each release on multiple machines and operating systems without any major incidents. As for challenges (common to recent releases) and lessons learned (about this update), read on.  [More]
				</description>
				
				<category>updates</category>
				
				<category>cf2021</category>
				
				<category>admin</category>
				
				<category>security</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<pubDate>Tue, 09 Sep 2025 23:23:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2025/9/9/coldfusion_updates_released_sep_9_2025</guid>
				
			</item>
			
			<item>
				<title>Announcing ColdFusion updates of July 8 2025 - p1 security update and more</title>
				<link>https://www.carehart.org/blog/2025/7/9/coldfusion_updates_released_jul_9_2025</link>
				<description>
				
				An update for ColdFusion has been released, July 8 2025, for each of cf2025 (update 3), cf2023 (update 15) and cf2021 (update 21).  In brief, it &lt;b&gt;addresses a number of P1 (Priority 1, &quot;Critical&quot;) security vulnerabilities&lt;/b&gt; and more, including bug fixes and some modest feature changes. 

As usual, there are a number of things you should consider before (or after) doing the update, with some discussed in Adobe&apos;s resources on the update (more than one), and some that I share below based on my experience helping people apply this and past updates. Finally, the update corrects some issues introduced in the previous updates, released in May.

In this post, I share the details about the update (from Adobe and from others). I can report I have installed the update for each release on multiple machines and operating systems without any major incidents. As for challenges (common to recent releases) and lessons learned (about this update), read on.  [More]
				</description>
				
				<category>updates</category>
				
				<category>cf2021</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<pubDate>Wed, 09 Jul 2025 23:45:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2025/7/9/coldfusion_updates_released_jul_9_2025</guid>
				
			</item>
			
			<item>
				<title>Announcing ColdFusion updates of May 13 2025 - p1 security update -  thoughts and resources</title>
				<link>https://www.carehart.org/blog/2025/5/14/coldfusion_updates_released_may_13_2025</link>
				<description>
				
				An update for ColdFusion has been released, May 13, 2025, for both cf2025 (update 2), cf2023 (update 14) and cf2021 (update 20). In brief, it &lt;b&gt;addresses a P1 (Priority 1, &quot;Critical&quot;) security vulnerability&lt;/b&gt;, as indicated in the associated &lt;a href=&quot;https://helpx.adobe.com/security/products/coldfusion/apsb25-52.html&quot;&gt;ASPB (security bulletin) for the update&lt;/a&gt;. 

The update &lt;b&gt;also incorporates potentially breaking changes (with Adobe trading compatibility for security), while it also includes configurable options to undo those changes (if you prefer to trade away security for compatibility)&lt;/b&gt;.  Finally, the update &lt;b&gt;corrects some issues introduced in the previous updates, released in April&lt;/b&gt;.

In this post, I share the details about the update (from Adobe and from others). I can report I have installed both updates on multiple machines and operating systems without incident. As for challenges or lessons learned, I may do a follow-up post as I/we all learn more.

For more details, read on.  [More]
				</description>
				
				<category>updates</category>
				
				<category>cf2021</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<pubDate>Wed, 14 May 2025 03:10:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2025/5/14/coldfusion_updates_released_may_13_2025</guid>
				
			</item>
			
			<item>
				<title>Delighted to be speaking at Into the Box 2025, in early May</title>
				<link>https://www.carehart.org/blog/2025/3/17/presenting_hidden_gems_in_fusionreactor</link>
				<description>
				
				I&apos;m delighted to announce that I&apos;ve been selected to speak at the upcoming &lt;a href=&quot;https://www.intothebox.org/&quot;&gt;Into the Box&lt;/a&gt; event (in DC in early May), where I&apos;ll be presenting &lt;b&gt;&quot;Hidden Gems in FusionReactor: for BoxLang, ACF, and Lucee Users&quot;&lt;/b&gt;.

This should not be confused of course with the &quot;Hidden Gems in CF2025&quot; talk which &lt;a href=&quot;https://www.carehart.org/blog/2025/3/15/presenting_hidden_gems_in_cf2025&quot;&gt;I also just announced&lt;/a&gt; that I&apos;d be presenting at the upcoming CF Summit East (next week in DC) and CFCamp (in Munich in late May). It&apos;ll be a busy few weeks! :-)

As with them, it&apos;s always a thrill to attend this annual event. Following is the topic description and more.  [More]
				</description>
				
				<category>presentations</category>
				
				<category>performance</category>
				
				<category>cf2016</category>
				
				<category>cf2021</category>
				
				<category>fusionreactor</category>
				
				<category>boxlang</category>
				
				<category>commandbox</category>
				
				<category>cf2025</category>
				
				<category>troubleshooting</category>
				
				<category>cf2023</category>
				
				<category>cf2018</category>
				
				<category>lucee</category>
				
				<pubDate>Mon, 17 Mar 2025 10:50:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2025/3/17/presenting_hidden_gems_in_fusionreactor</guid>
				
			</item>
			
			<item>
				<title>A table of Java versions supported by given ColdFusion versions</title>
				<link>https://www.carehart.org/blog/2025/3/13/table-of-java-to-cf-versions</link>
				<description>
				
				[Posted originally in Mar 2025, updated in May 2026)

Now that CF2025 &lt;a href=&quot;https://www.carehart.org/blog/2025/2/25/coldfusion_2025_released&quot;&gt;has come out&lt;/a&gt;, supporting Java 21--and as ColdFusion and Java versions continue to evolve--you may wonder which version(s) of Java you can use with your current (or a given) version of ColdFusion. 

You can&apos;t just use &quot;any&quot; jvm version with CF: &lt;strong&gt;it depends on first on what version of CF you are using&lt;/strong&gt;, and then may even depend on what CF update has been applied to that CF version. (You also can&apos;t use Java from any vendor: Adobe supports only use of Oracle Java, and they license it for our use, as I discuss later.) And to be clear, currently ONLY CF2025 supports Java 21. (And though Java 25 came out in Sep 2025 as the latest LTS or &quot;long-term support&quot; Java releases, note that NO CF version currently supports that--as of an updated check in May 2026.)

So in this post, &lt;strong&gt;I offer a table that clarifies things, &lt;/strong&gt;listing the various recent CF versions (even those no longer supported) and what (LTS) Java versions they supported, including if some CF update of a version changes the Java version supported.  [More]
				</description>
				
				<category>cf2016</category>
				
				<category>cf2021</category>
				
				<category>cf10</category>
				
				<category>java</category>
				
				<category>cf11</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<category>cf2018</category>
				
				<pubDate>Thu, 13 Mar 2025 23:57:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2025/3/13/table-of-java-to-cf-versions</guid>
				
			</item>
			
			<item>
				<title>ColdFusion 2025 released, Feb 25 2025 - resources and my initial thoughts</title>
				<link>https://www.carehart.org/blog/2025/2/25/coldfusion_2025_released</link>
				<description>
				
				ColdFusion 2025 has been released today, Feb 25 2025. In this post I am not only helping share news of the release, and pointing to available resources, but I also share some thoughts/observations on related matters that may be a bit challenging for most to find more about on their own (if they may only assess a couple of resources, or hear only tidbits shared in social media). 

First, for more on the many features and changes, I share many Adobe resources--about which I also offer some additional comment. I also discuss changes regarding OS and DB support as well as the fact that &lt;b&gt;CF2025 now runs on Java 21&lt;/b&gt;-- and that the traditional server deployment of CF comes installed atop &lt;b&gt;Tomcat 10.1&lt;/b&gt;. I then share still more info on other matters and resources related to the new version.

I then focus on &lt;b&gt;the major change in licensing, for CF2025 and forward, to being subscription only&lt;/b&gt;--which I&apos;ll note has no effect on those currently running CF2023 or earlier. I share pricing info and also help in assessing differences in the EULA, and more.

Finally I discuss some &lt;b&gt;migration considerations&lt;/b&gt;--including important &lt;b&gt;REMOVAL of some older features from CF2025&lt;/b&gt;, as CF continues to be made more secure and modernized. I also identify tools and resources to help aid you in that migration, when you&apos;re ready to begin attempting it. 

For all that and more, read on.  [More]
				</description>
				
				<category>tomcat</category>
				
				<category>IIS</category>
				
				<category>admin</category>
				
				<category>licensing</category>
				
				<category>installation</category>
				
				<category>security</category>
				
				<category>news</category>
				
				<category>docker</category>
				
				<category>cf2025</category>
				
				<category>cf2023</category>
				
				<category>apache</category>
				
				<pubDate>Tue, 25 Feb 2025 19:55:00 -0500</pubDate>
				<guid>https://www.carehart.org/blog/2025/2/25/coldfusion_2025_released</guid>
				
			</item>
			</channel></rss>