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

ColdFusion (2025 release) Update 12

Last update:
Aug 11, 2026
ColdFusion (2025 release) Update 12 tech note

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.
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 (2025 release) Updates for more information.

What's new and changed

ColdFusion (2025 release) Update 12 (release date: August 11, 2026) resolves critical, important, and moderate vulnerabilities that could lead to arbitrary code execution, arbitrary file system read, privilege escalation, security feature bypass, and memory exposure.
This update also contains an upgraded Tomcat version 10.1.57.
View the security bulletin, APSB26-90, for more information.

Enhancements in this release

New JVM flag
  • -Dcoldfusion.xml.saxon.allowCollection
  • -Dcoldfusion.debugger.bindhost
  • -Dcoldfusion.websocket.requireAuthForInvoke
Learn more about the new flags in JVM arguments in ColdFusion (2025 release) updates.
New Application.cfc flag
this.wsRequireAuthForInvoke
This flag controls whether a WebSocket client must be authenticated before it can invoke access="remote" CFC methods over the channel. By default, its value is True.
By default, ColdFusion requires a WebSocket connection to be authenticated, either by returning true from an onWSAuthenticate handler, or through CF authentication, before it will process any CFC method invocation requested by that client. Requests from unauthenticated connections are rejected.
Setting this value to false disables this requirement, allowing CFC methods to be invoked over the channel without prior authentication.
Learn more about the flag in Application variables in ColdFusion.
Note: WebSocket CFC invocation (invoke and invokeAndPublish) now requires an authenticated connection by default. Applications that set this.wsRequireAuthForInvoke = false retain the old (unauthenticated-allowed) behavior.
New config file property
ccssecretkeyfingerprint in cfusion/lib/ccs/ccs.properties
The CCS key is now generated per installation using SecureRandom and bound to an environment fingerprint. It is regenerated when a system is cloned or restored from an image, preserved across restarts on the same host, and generated independently by each cluster node.
VS Code plugin update
Learn more about the update in Update 7 of the CF Builder extension for VS Code.
Performance Monitoring Toolset update
Learn more about the changes in ColdFusion (2025 release) Performance Monitoring Toolset Update 2.

Bugs fixed in the update

Addressed a stored cross-site scripting (XSS) vulnerability in the CKEditor file-manager upload feature. The upload filter previously relied on a denylist of disallowed extensions that did not block active client-side content such as .html, allowing an attacker to upload a page that executed script on the application's origin and, in a chained scenario, could lead to remote code execution. File-upload validation is now allowlist-based: uploads are restricted to a fixed set of inert, non-executable file types (common image, document, and media formats), and all other extensions, including HTML and script files, are rejected. File uploads remain disabled by default.

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
  • 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. MD5: 1aaf432b9ae7050c193dd2fbc81b7f47
  2. Download the packages zip (MD5: eefdaab30ffb709212b17284cbe0bf4f) 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-012-331922.jar
     
  • Linux-based platforms: <cf_root>/jre/bin/java -jar  <InstallerRepositoryUnzippedPath>/bundles/updateinstallers/hotfix-012-331922.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,12,331922

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-00012-331922/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-00012-331922}/backup directory to {cf_install_home}/{instance_name}/
Note:
Uninstalling this update only removes the core update itself. Any ColdFusion packages that were updated as part of this release remain at their latest compatible versions. If you need to revert package versions, you must do so separately; uninstalling the core update does not roll back package versions automatically.
Frequently asked questions
If I uninstall ColdFusion 2025 Update 12, will all the packages installed with it be rolled back?
No. Package rollback depends on the minimum core dependency of each package:
  • Packages with a minimum core dependency of update 12 (that is, they specifically require this core level) are rolled back when you uninstall this core update.
  • Packages with a minimum core dependency of Update 10 or Update 11 remain installed at their latest compatible versions and are not automatically rolled back when you uninstall the core update.

Connector configuration

2025 UpdateConnector recreation required
Update 12No
Update 11No
Update 10No
Update 9No
Update 8No
Update 7No
Update 6No
Update 5No
Update 4No
Update 3
No
Update 2No
Update 1No

Package updates

2025 UpdatePackages updated
Update 12
Yes
  • adminapi
  • administrator
  • ajax
  • ai
  • debugger
  • pmtagent
  • websocket
Update 11
Yes
  • administrator
  • debugger
  • document
  • pdf
  • htmltopdf
  • presentation
  • print
  • report
  • websocket
Update 10
Yes
  • administrator
  • ajax
  • exchange
  • feed
  • mail
  • websocket
  • ai
Update 9
Yes
  • administrator
  • ccs
  • exchange
  • mail
Update 8
Yes
  • ai
Update 7
Yes
  • adminapi
  • administrator
  • CCS
Update 6
Yes
  • image
  • htmltopdf
  • msgraph
  • pdf
  • print
  • search
Update 5
Yes
  • administrator
  • ccs
  • document
  • htmltopdf
  • pdf
  • presentation
  • print
  • report
  • scheduler
  • search
  • spreadsheet
  • websocket
Update 4
Yes
  • feed
Update 3
The following packages are updated:
  • adminapi
  • administrator
  • axis
  • document
  • htmltopdf
  • pdf
  • presentation
  • print
  • report
  • scheduler
  • search
  • sharepoint
  • spreadsheet
Update 2
The following packages are updated:
  • adminapi
  • administrator
  • document
  • htmltopdf
  • pdf
  • presentation
  • print
  • report
  • scheduler
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