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

ColdFusion (2025 release) Update 1

Last update:
May 18, 2026
ColdFusion (2025 release) Update 1

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:
Check if you need to create and configure connectors after installing the update. View the section Connector Configuration Table for more information.

What's new and changed

ColdFusion (2025 release) Update 1 (release date, April 8, 2025) resolves  several critical and important vulnerabilities that could lead to arbitrary file system read, arbitrary code execution, and security feature bypass.
View the security bulletin, APSB25-15, for more information.
Note:
With this update, the serialfilter.txt file present in cfusion/lib will be replaced. So if you already have custom entries added to the file, copy the custom entries from the backup file (cfusion/hf-updates/{version}/backup/lib).

New JVM flag in this update

By default, the request timeout when converting a document into a PDF is 60 seconds. However, if the conversion exceeds 60 seconds, there is a timeout. In this update, ColdFusion has introduced the JVM flag -Dcoldfusion.pdfg.connectionTimeout, which helps you change the timeout value. The value of the flag is in milliseconds. Also, use this flag to reduce intermittent timeout error in PDF Engine 2.0.
View JVM arguments in ColdFusion (2025 release) for more information on the flags.

Add-on installers

In this update, the add-on installers are refreshed. If you're using the standalone PDFg service, you must reinstall the add-on.
If you want to learn more about securing Solr, see this blog.
Find the refreshed installers in ColdFusion downloads.

Known issues in the update

  • If you encounter an issue when using PDF Engine 1.0 on Linux, you can either switch to PDF Engine 2.0 or set up the service on Windows and access it remotely.
  • Sometimes, you are unable to create a PDF due to PDFg service authentication failure. As a workaround, update the service manager and retry creating the PDF.
  • If you encounter the error message, "java.lang.NoClassDefFoundError: coldfusion/document/DocumentScope" while publishing a document to PDF using PDF Engine 1 and 2, then clear the Felix cache and restart ColdFusion.
  • NullPointerException occurs when executing the CLI command using the ColdFusion Docker image-docker run --rm -it -v ./mywebroot:/app -e acceptEULA=YES adobecoldfusion/coldfusion:latest cli file.cfm. After ColdFusion starts, run CLI from the container.
  • If the file jetty-ipaccess.xml is not present in <cf_root>/cfusion/jetty/etc folder, create one with the steps incfhtmltopdf, and restart Jetty server.

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 2025 (version 2025.0.0.331385)

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-001-331420.jar
  • Linux-based platforms:<cf_root>/jre/bin/java -jar  <InstallerRepositoryUnzippedPath>/bundles/updateinstallers/hotfix-001-331420.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.

Post installation

Note:
After applying this update, the ColdFusion build number should be 2025,0,01,331420

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-2025-00001-331420/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-2025-00001-331420}/backup directory to {cf_install_home}/{instance_name}/

Connector configuration

2025 UpdateConnector recreation required
Update 1No

Package updates

2025 UpdatePackages updated
Update 1
The following packages are updated:
  • administrator
  • ajax

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