Whatever message this page gives is out now! Go check it out!

ColdFusion (2023 release) Update 15

Last update:
May 18, 2026
ColdFusion (2023 release) Update 15

Security recommendations

For all security updates, Adobe recommends applying the security configuration settings outlined on the ColdFusion Security page and reviewing the respective Lockdown guides.
Warning:
In ColdFusion (2023 release) Update 15, Tomcat has been upgraded from version 9.0.72 to 9.0.106. This upgrade includes important bug fixes, performance improvements, and security enhancements from the Tomcat project.
Note:
The updates below are cumulative and contain all updates from previous ones. If you are skipping updates, you can apply the latest update, not those you are skipping. Further, you must take note of any changes that are implemented in each of the updates you are skipping.
View ColdFusion (2023 release) Updates for more information.

What's new and changed

ColdFusion (2023) Update 15 includes important security fixes that mitigate vulnerabilities related to arbitrary file reads, code execution, privilege escalation, and security feature bypass.
The update also upgrades the underlying Tomcat engine to version 9.0.106 and resolves several issues reported in earlier updates.
View the security bulletin, APSB25-69, for more information.
Warning:
If your ColdFusion server instance is registered as a client with the Central Configuration Server (CCS), you will need to re-register the instance after applying Update 3 by running the deletenode command followed by addnode. This step is not required for CCS nodes that are child ColdFusion instances.
Note:
If you have added custom entries to the pathfilter.json file for scheduled task output file allowlisting, you must either:
  • Back up the pathfilter.json file before applying the update, or
  • Restore it from the update backup after applying the update.
The backup copy of the file can be found at: hf-updates\hf-2023-00015-330825\backup\lib\pathfilter.json

New JVM flags in this update

  • -Dcoldfusion.xml.allowExternalEntities
View JVM arguments in ColdFusion (2021 release) for more information on the flags.

OEM upgrades

LibraryOlder versionUpdated version
Tomcat9.0.729.0.106
Apache POI3.17, 4.1.25.4.1
Apache XMLBeans3.1.05.3.0
Apache Commons IO2.15.12.19.0
Apache Commons Compress1.191.26.2

Changes to remote methods

The remote method changes done in previous update is now limited to remote CFC calls only and does not apply to regular (local) method invocations.

Bug fixes in this update

  • The lockdown installer used a ColdFusion component (lockdown.cfc) located in the CFIDE/lockdown directory to complete the setup process. Due to security changes introduced in a previous update, the installer worked unexpectedly if remote methods in the component were blocked during execution.
  • In the previous update, using returnformat and queryformat in remote methods resulted in errors due to changes requiring all arguments to be explicitly declared.
  • The warning message in log file contains a typo. It says "bytecodeexectuionpaths" instead of "bytecodeexecutionpaths".
  • On non-Windows systems, editing the local PDF service from the ColdFusion Administrator removes the service because the IP address 127.0.0.1 is not included in the jetty/etc/jetty-ipaccess.xml allowed list. After installing ColdFusion and applying the latest update, navigating to the PDF Service page and modifying the local configuration results in the service being deleted instead of updated. The expected behavior is for the configuration to be saved without removing the service.
  • The CAR (ColdFusion Archive) build process fails if the cfusion/packages directory does not exist, as the CAR file must be placed specifically within this folder. Instead of automatically creating the missing directory, the build terminates with an error. The expected behavior is for the process to create the packages folder if it's not already present.
  • In some cases, scheduled tasks are deleted if the "Publish to a log file" option is enabled. The issue occurs after creating a scheduled task with logging enabled and applying the latest update. Even after adding the exception and restarting ColdFusion, the deleted task isn't restored.
  • In some cases, you are unable to generate an encrypted PDF. An error "NoClassDefFoundError: org.bouncycastle.asn1.DEREncodable" appears in logs and PDF generation aborts with a Java class‐loading error for BouncyCastle.
  • <cfdocument> failed to embed registered fonts in generated PDF files. Even after registering the fonts, the output PDF defaulted to using MS Mincho, which was not embedded. This resulted in missing text, particularly for languages like Japanese on systems such as Linux that do not include the MS Mincho font. With this fix, registered fonts are now properly embedded in the PDF output.

Known issues in the update

  • After applying the update, you may encounter an error message on pages that use cfmail. View the discussion for more information. As a workaround:
    • Stop Coldfusion
    • Delete the Felix cache (cfusion/bin/felix-cache)
    • Restart Coldfusion

Prerequisites

  1. On 64-bit computers, use 64-bit JRE for 64-bit ColdFusion.
  2. If the ColdFusion server is behind a proxy, specify the proxy settings for the server to get the update notification and download the updates. Specify proxy settings using the system properties below in the jvm.config for a stand-alone installation, or corresponding script file for JEE installation.
    • http.proxyHost
    • http.proxyPort
    • http.proxyUser
    • http.proxyPassword
  3. For ColdFusion running on JEE application servers, stop all application server instances before installing the update.

ColdFusion JDK flag requirements

COLDFUSION 2023 (version 2023.0.0.330468) and above

For Application Servers

On JEE installations, set the following JVM flag, " -Djdk.serialFilter= !org.mozilla.**;!com.sun.syndication.**;!org.apache.commons.beanutils.**;!org.jgroups.**;!com.sun.rowset.**; !com.mysql.cj.jdbc.interceptors.**;!org.apache.commons.collections.**;", in the respective startup file depending on the type of Application Server being used.
For example:
  • Apache Tomcat Application Server: edit JAVA_OPTS in the ‘Catalina.bat/sh’ file
  • WebLogic Application Server: edit JAVA_OPTIONS in the ‘startWeblogic.cmd’ file
  • WildFly/EAP Application Server: edit JAVA_OPTS in the ‘standalone.conf’ file
Set the JVM flags on a JEE installation of ColdFusion, not on a standalone installation.

Installation

ColdFusion Administrator

In Package Manager > Packages, click Check for Updates in Core Server.
After it detects an update, click Update. The core package gets updated the the latest update.
All installed packages also get updated.
Restart ColdFusion for the changes to take effect.

Install the update in offline mode manually

  1. Download the hotfix installer from the link.
  2. Download the packages zip file from this link and extract its contents to a location accessible to all ColdFusion server instances.
  3. Update "packagesurl" in cfusion/lib/neo_updates.xml of cfusion and all its child instances to point to <InstallerRepositoryUnzippedPath>/bundles/bundlesdependency.json present inside the downloaded folder.
You must have privileges to start or stop ColdFusion service and full access to the ColdFusion root directory.
  • Windows:<cf_root>\jre\bin\java.exe -jar <InstallerRepositoryUnzippedPath>\bundles\updateinstallers\hotfix-015-330825.jar
  • Linux-based platforms:<cf_root>/jre/bin/java -jar  <InstallerRepositoryUnzippedPath>/bundles/updateinstallers/hotfix-015-330825.jar
If the core server hotfix installation is successful and if there are errors or issues with packages, packages can be installed/updated from the package manager client(cfusion\bin\cfpm.bat|cfpm.sh).
Ensure that the JRE bundled with ColdFusion is used for executing the downloaded JAR. For standalone ColdFusion, this must be at, <cf_root>/jre/bin.
Install the update from a user account that has permissions to restart ColdFusion services and other configured webservers.
For further details on manually updating the application, see the help article.
Note:
If you are on Java 17.0.8 or higher and want to apply the Hotfix manually, use the flag java -Djdk.util.zip.disableZip64ExtraFieldValidation=true -jar hotfix.jar.
However, if you are applying the update from the Administrator, you do not require any flag.

Post installation

Note:
After applying this update, the ColdFusion build number should be 2023,0,15,330825

Uninstallation

To uninstall the update, perform one of the following:
  • In ColdFusion Administrator, click Uninstall in Server Update > Updates > Installed Updates.
  • Run the uninstaller for the update from the command prompt. For example, java -jar {cf_install_home}/{instance_home}/hf_updates/hf-2023-00015-330825/uninstall /uninstaller.jar
If you can't uninstall the update using the above-mentioned uninstall options, the uninstaller could be corrupted. However, you can manually uninstall the update by doing the following:
  1. Delete the update jar from {cf_install_home}/{instance_name}/lib/updates.
  2. Copy all folders from {cf_install_home}/{instance_name}/hf-updates/{hf-2023-00015-330825}/backup directory to {cf_install_home}/{instance_name}/

Connector configuration

2023 UpdateConnector recreation required
Update 15
No
However, upgrading from Update 4 and earlier requires you to recreate the connector.
View the following for more information on creating and configuring connectors:
Update 14
No
However, upgrading from Update 4 and earlier requires you to recreate the connector.
View the following for more information on creating and configuring connectors:
Update 13
No
However, upgrading from Update 4 and earlier requires you to recreate the connector.
View the following for more information on creating and configuring connectors:
Update 12
No
However, upgrading from Update 4 and earlier requires you to recreate the connector.
View the following for more information on creating and configuring connectors:
Update 11
No
However, upgrading from Update 4 and earlier requires you to recreate the connector.
View the following for more information on creating and configuring connectors:
Update 10
No
However, upgrading from Update 4 and earlier requires you to recreate the connector.
View the following for more information on creating and configuring connectors:
Update 9
No
However, upgrading from Update 4 and earlier requires you to recreate the connector.
View the following for more information on creating and configuring connectors:
Update 8
No
However, upgrading from Update 4 and earlier requires you to recreate the connector.
View the following for more information on creating and configuring connectors:
Update 7No
However, upgrading from Update 4 and earlier requires you to recreate the connector.
View the following for more information on creating and configuring connectors:
Update 6
No
However, upgrading from Update 4 and earlier requires you to recreate the connector.
View the following for more information on creating and configuring connectors:
Update 5Yes
Update 4No
Update 3No
Update 2No
Update 1No

Package updates

UpdatePackages updated
Update 15
Yes
The following packages are updated:
  • adminapi
  • administrator
  • axis
  • document
  • exchange
  • htmltopdf
  • image
  • pdf
  • presentation
  • print
  • report
  • saml
  • scheduler
  • search
  • sharepoint
  • spreadsheet
Update 14
Yes
The following packages are updated:
  • adminapi
  • administrator
  • document
  • htmltopdf
  • pdf
  • presentation
  • print
  • report
  • scheduler
Update 13
Yes
The following packages are updated:
  • htmltopdf
  • administrator
  • ajax
  • ccs
Update 12
Yes
The pmtagent package is updated.
Update 11Yes
Update 10No
Update 9No
Update 8Yes
Update 7Yes
Update 6No
Update 5Yes
Update 4No
Update 3No
Update 2No
Update 1No

Share this page

Was this page helpful?
We're glad. Tell us how this page helped.
We're sorry. Can you tell us what didn't work for you?
Thank you for your feedback. Your response will help improve this page.

On this page