Skip to main content
Community Manager
September 9, 2025

NOW LIVE! ColdFusion 2025, 2023, and 2021 September security updates

  • September 9, 2025
  • 5 replies
  • 2750 views

We are pleased to inform you that we've released security updates for ColdFusion 2025, 2023, and 2021 releases. For more information, see the respective tech notes:

The updates address an important security fix related to critical path traversal.

View the security bulletin, APSB25-93, for more information.

 

Download the updates

 

Docker and CFFiddle

 

Please download and apply the updates and provide your feedback.

    5 replies

    Participant
    November 20, 2025

    I ran the Update 22 for CF-2021 on Windows-2019 server from the Package manager. 

    The Update log reported all Success and no Errors or warnings. Yet the last line from coldfusion-out.log was:
       -- Unable to install Logging package: java.lang.NoSuchMethodError: org.apache.logging.log4j.util.LoaderUtil.getClassLoaders()[Ljava/lang/ClassLoader;
    The Coldfusion Application service starts in Windows as usual, but all sites, including CFAdmin, are down with 500 errors. There are no application.log, server.log, or cf-out.logs any more, just cf-error.log. Upgrading all CF web server connectors with Web Config. Tool, as Charlie Arehart recommended, also didn't help. 
    I wonder if anyone can suggest how I should address the problem?
     
    This is the first error in the coldfusion-error.log after restarting the Service:
    Nov 19, 2025 5:59:01 AM org.apache.catalina.core.ApplicationContext log
    INFO: ColdFusionStartUpServlet: ColdFusion: VM version = 11.0.11+9-LTS-194
    java.lang.NoSuchMethodError: org.apache.logging.log4j.util.LoaderUtil.getClassLoaders()[Ljava/lang/ClassLoader;
    at org.apache.logging.log4j.core.impl.ThreadContextDataInjector.getProviders(ThreadContextDataInjector.java:252)
    at org.apache.logging.log4j.core.impl.ThreadContextDataInjector.access$000(ThreadContextDataInjector.java:53)
    at org.apache.logging.log4j.core.impl.ThreadContextDataInjector$ForDefaultThreadContextMap.<init>(ThreadContextDataInjector.java:74)
    at org.apache.logging.log4j.core.impl.ContextDataInjectorFactory.createDefaultInjector(ContextDataInjectorFactory.java:91)
    at org.apache.logging.log4j.core.impl.ContextDataInjectorFactory.createInjector(ContextDataInjectorFactory.java:71)
    at org.apache.logging.log4j.core.lookup.ContextMapLookup.<init>(ContextMapLookup.java:34)
    at org.apache.logging.log4j.core.lookup.Interpolator.<init>(Interpolator.java:126)
    at org.apache.logging.log4j.core.config.AbstractConfiguration.<init>(AbstractConfiguration.java:129)
    at org.apache.logging.log4j.core.config.NullConfiguration.<init>(NullConfiguration.java:32)
    at org.apache.logging.log4j.core.LoggerContext.<clinit>(LoggerContext.java:86)
    at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.createContext(ClassLoaderContextSelector.java:233)
    at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.locateContext(ClassLoaderContextSelector.java:206)
    at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:135)
    at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:228)
    at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
    at org.apache.logging.log4j.LogManager.getContext(LogManager.java:176)
    at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:666)
    at org.apache.logging.log4j.LogManager.getRootLogger(LogManager.java:700)
    at coldfusion.log.LogService.loadLoggers(LogService.java:717)
    at coldfusion.log.LogService.start(LogService.java:188)
    at coldfusion.server.CFService.setupLogger(CFService.java:427)
    at coldfusion.server.CFService.start(CFService.java:1701)
    at coldfusion.server.j2ee.CFStartUpServlet.startCFService(CFStartUpServlet.java:609)
    at coldfusion.server.j2ee.CFStartUpServlet.init(CFStartUpServlet.java:552)
    at javax.servlet.GenericServlet.init(GenericServlet.java:143)
    at coldfusion.bootstrap.ClassloaderHelper.initServletClass(ClassloaderHelper.java:137)
    at coldfusion.bootstrap.BootstrapServlet.init(BootstrapServlet.java:111)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:989)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:946)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:843)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4290)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4591)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1203)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1193)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:76)
    at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:749)
    at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:721)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1203)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1193)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:76)
    at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:749)
    at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:211)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)
    at org.apache.catalina.core.StandardService.startInternal(StandardService.java:412)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)
    at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:874)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)
    at com.adobe.coldfusion.launcher.Launcher.run(Launcher.java:1035)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at com.adobe.coldfusion.bootstrap.Bootstrap.init(Bootstrap.java:114)
    at com.adobe.coldfusion.bootstrap.Bootstrap.main(Bootstrap.java:241)
    java.lang.NoClassDefFoundError: Could not initialize class org.apache.logging.log4j.core.LoggerContext
    at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.createContext(ClassLoaderContextSelector.java:233)
     
    Also each isapi-redirect.log says: "Tomcat is probably not started".
    Charlie Arehart
    Community Expert
    Community Expert
    November 20, 2025

    That's certainly a dismaying situation to be in. Let's see if we can get you going.

     

    First, I see no connection between your error and the suggestion to run the wsconfig tool. They're unrelated. 

     

    Second, while you confirm that the update log reports all successes (the table at about line 70), please also see THE BOTTOM of that log, where about 10 lines from the bottom it reports what packages (if any) were to be downloaded, and if those downloads worked. Any problems there? 

     

    But as is also reported there (toward the end of that line), the packages are not UPDATED until cf is started. 

     

    So next look at that coldfusion-out.log, finding the lines from the time cf was started after that update. Watch closely for errors there. (You'd shared what was shown at the bottom of that log.) Let us know what you find.

     

    Your problem should be in one place or another. Or there may be more to your situation than you've shared. For instance, what update were you on before this one? Also, when you say there are no other logs, do you mean no others are being updated? Or that logs which WERE there have somehow disappeared? 

     

    Finally, solving an outage like this via back-and-forth here can be quite challenging (like playing the old game battleship). And given your urgency, we might solve this in a fraction of the time in a shared desktop consulting session. If you'd like to be up again ASAP, I'm available immediately. For more on my rates, approach, satisfaction guarantee, online calendar, email, phone, and more, see the consulting page at carehart.org.

    /Charlie (troubleshooter, carehart. org)
    Charlie Arehart
    Community Expert
    Community Expert
    November 20, 2025

    Also, while I didn't immediately see a potential connection, we should ask if you have tried clearing the felix-cache (stop cf, delete the cfusion/bin/felix-cache folder, then start cf).

     

    That's not recommended in the update technote of each update, but even so it's always worth doing, especially when an update may implement package updates. 

    /Charlie (troubleshooter, carehart. org)
    Participating Frequently
    September 10, 2025

    I just patched my DIT server from 21 to 22, and I noticed something strange.  After copying the contents of hotfix-packages-cf2021-022-330451.zip into my bundles directory, I ran the update via CFAdmin.  It all looked good, but then I got an error saying the mail module wasn't installed.  When I tried to install it manually, it failed because a bunch of files were no longer in the repo subdirectory -- they were the bcp* files (such as bcmail-jdk15on-153.jar and bcpkix-jdk15on-153.jar).  These files absolutely did exist in the repo directory, but after the core install, they were deleted.

    I verified the exact behavior with my FIT server.  The same files were deleted after the core installation.

    Charlie Arehart
    Community Expert
    Community Expert
    September 10, 2025

    Critic, I'll confirm I saw that also--on one cf2025 machine (only one, among a few cf2025 updates I've done since yesterday).

     

    FWIW, I found that the files in question were identified first as missing in errors shown during the cf startup (after the update) in the coldfusion-out.log. Then I also saw them listed as files REMOVED by the update itself, as tracked in the hotfixfilelist.log, found in the hf-updates folder for that cf update. These removed files matched those listed as missing in the startup.

     

    And like you, I "put them back" in the cf bundles/repo, as they were saved during the update in the hf-updates folder for the update, in its backup/bundles folder. Then the restart showed no errors in the coldfusion-out.log. 

     

    It's not clear to me now why this would have happened on that one server and not the other cf2025 (nor cf2023 or cf2021) instances I updated, when they all were installed with the same (Windows) installer, each having all packages implemented, and each updated when a new update came out.

     

    Just sharing those distinctives, if it may help others looking into it. Until then, hope the steps I offer may help someone. 

    /Charlie (troubleshooter, carehart. org)
    Participating Frequently
    September 10, 2025

    There's still something wrong here -- it's still not sending emails, though now I'm not getting the error outright.

     

    I'm rolling back to 21 and will wait to move to 22 until the bugs are flushed out.

    Participating Frequently
    September 10, 2025

    This is not appearing in the CF admin updates?

     

    https://www.adobe.com/go/coldfusion-updates

     

    There appears to be no HF 22 for 2021 listed in this?

     

    Was it removed?

    Charlie Arehart
    Community Expert
    Community Expert
    September 10, 2025

    @w49369461 that url is indeed "working" for many and showing references to yesterday's update within the xml itn returns. As I noted just now in a reply to a_1001, some people seem to experience a lag in the updated content appearing to them, for whatever reason (web caches, cdn's, etc) . The complaints about it usually passes within a day of the update. 

     

    Have you tried the url from your phone or home? Does it have a reference to "- 022", for instance, which is part of the string describing update 22 of cf2021?

     

    If so, you could then follow the steps to "Install the update in offline mode manually" as outlined in each update's technote. In this case you'd download the needed files (whose links are offered in the technote) onto that other machine , then copy them to the CF machine to be updated. Not fun, I realize. Or wait to see if the web caching issues clear for you. 

    /Charlie (troubleshooter, carehart. org)
    Participating Frequently
    September 10, 2025

    We have tried it from a number of locations. We have never experienced the cache lasting this long, which is why I made the comment. Just in case it is a legit issue that Adobe were not aware of.

    Not seing the update on any UK devices. Servers, phones, laptops, all on various connections.  So I assume its a CDN cache. 

    We will wait for a day to see if turns up, prefer this over manually doing it.

     

    Participating Frequently
    September 9, 2025

    Was the feed package also updated with this update? I am seeing inconsistencies where 2023.0.16.330828 is available for download, but it is not the same over all our instances.

    I am also seeing issues where some of our instances are unable to download 2023 update 16 and it *appears* to be a problem with the CDN that is hosting the https://cfdownload.adobe.com/pub/adobe/coldfusion/xml/updates.xml update information.

    Locally, when going to the above link I can see Update 16, but on our servers and in the CF administrator it is not allowing the download of 16. When visiting the link above on our servers it does not list update 16 in the xml.

    Charlie Arehart
    Community Expert
    Community Expert
    September 9, 2025

    Chuck, 2 things.

     

    1) First, uep, as for your "inconsistencies" about accessing the URLs (or what's returned from them), that's a common problem for some (not everyone) in the first hours or even day after these updates are released. I assume Adobe is using some CDN, yes, or some other sort of caching within their large enterprise architecture. Sadly, some may be out of our hands (and the CF teams's.

     

    I do find it odd that some have the problems and others don't--which makes me think it's more NOT about Adobe's server's or architecture, per se. But who can know? 🙂

     

    2) Also yes: the feed package was updated for CF2023.

     

    And it may help to know that Adobe does in fact offer a table at the bottom of each update technote which lists what packages are due to be updated along with the core update, for each update. (And another after that listing whether the web server connector needed to be updated, per each update.)

     

    Of course, if one SKIPs any updates, then you get updates to whatever packages are listed below that as well, for the updates you skipped.

     

    Better still, one could look in the CF Admin to see what packages it may list as "to be updated". Of course, some may not pay notice it--and others run the update from the commandline, not even seeing the Admin.

     

    For either of them, one can look to the update log (created for each update, within the cfusion/hf-updates folder for the update applied). As some may know, that shows first (at about line 70) how many "successes" and "fatalerrors" happened in the update. And THEN it also lists (several lines up from the bottom) what packages (if any) were downloaded (to be updated).

    And as some may know, those are then updated NOT at THAT time (during the CF update) but on the next start of CF AFTER the update. And one can see in the coldfusion-out.log that during that next startup, it will show first "uninstalling" packages and associated jars, but it won't show "installing" them. It will just show them being "started".

     

    Each of those are useful to watch after each update.  🙂

    /Charlie (troubleshooter, carehart. org)
    Inspiring
    September 9, 2025

    I'm getting 404 errors on the download links for the Hotfix and Packages repositories. The URLs look OK, but I keep getting the message "The requested URL /pub/adobe/coldfusion/2021/packages/hotfix-packages-cf2021-022-330451.zip was not found on this server." (Same with 2025)  Could you check to make sure the paths are right? Thanks!

    Charlie Arehart
    Community Expert
    Community Expert
    September 9, 2025

    @wtlaughlin , I am not finding the link to that update jar to fail. I can offer the working link, and then below that I report a problem of a link that IS incorrect in another page about cf2023's update 16.

     

    1) As you may have noticed, the link you show is missing a domain name. Have you tried it as the full URL, https://cfdownload.adobe.com/pub/adobe/coldfusion/2021/packages/hotfix-packages-cf2021-022-330451.zip? That works for me. If it works, great.

    As for where you found the bad link, I'll note that I don't see that shortened version (without the domain name) in any of the pages offering that download (which would be either the CF2021 update 22 technote or the page listing all the cf2021 updates (and those links for each). Can you say where you found it?

     

    2) Then again, as a note to Saurav (who handles the docs) and other readers here: note that I DO find a mistaken link in the page of cf2023 updates for the CF2023 update 16 jar.  It offers the link as https://cfdownload.adobe.com/pub/adobe/coldfusion/2023/updates/hotfix-015-330828.jar , but see the mistake: it refers to 015 rather than 016—but the numbers following it are correct for the build number, so just changing that 15 to 16 works: https://cfdownload.adobe.com/pub/adobe/coldfusion/2023/updates/hotfix-016-330828.jar  

     

    I confirmed that the links to the jar and zip as offered in the 3 release update technotes are correct, as are all the other links for today's updates in the pages that list all the updates for each release, with their file download links (but this one problem in my point 2 above).

     

    It's a lot for Saurav to juggle, of course. As always, just trying to help (him and other readers).

    /Charlie (troubleshooter, carehart. org)
    Community Manager
    September 9, 2025

    Thanks Charlie. I've updated the link.