This post is to announce the release of ColdFusion 11 Update 11 and ColdFusion 10 Update 22.
Update 11 and Update 22 fix approximately 164 and 45 bugs respectively. For the list of bugs fixed in these updates, refer the following documents:
Bugs fixed with Update 11
Bugs fixed with Update 22

Follow the steps below to apply the updates:

  1. Navigate to ColdFusion Administrator -> Server Updates -> Updates.
  2. Switch to the "Settings" tab.
  3. Ensure that the update site URL is set to the right value by clicking on the "Restore Default URL" button.
  4. Click on "Submit changes" to save your changes.
  5. Switch to "Available Updates" tab. Click on "Check for Updates".
  6. "ColdFusion 11 Update 11" or "ColdFusion 10 Update 22" should be listed under the "Available updates" tab. 
  7. Click on the "Download and Install" button to install the update.

Refer the following technotes for instructions and other details related to the updates:

ColdFusion 11 Update 11 technote 
ColdFusoin 10 Update 22 technote

To apply these updates manually, download the required update by clicking on one of the applicable links below:

ColdFusion 11 Update 11 jar
ColdFusoin 10 Update 22 jar
To run the downloaded jar, execute the following command:
java -jar <jar-file-dir>/hotfix_0xx.jar
You should use the JRE used by ColdFusion for running the update jar (for standalone CF, it should be <cf_root>/jre/bin)
For further details on the manual application of the updater follow this help article.
The build number after applying this update should be:
11,0,11,301867 for ColdFusion 11;
10,0,22,301868 for ColdFusion 10.

8 Comments to “ColdFusion 11 Update 11 and ColdFusion 10 Update 22 released”

  1. Tom Chiverton
    All the detailed bug links link to a page with a giant scary warning message saying the web site is about to shut down.

  2. Piyush
    We are moving to a new bug reporting tool called "Tracker". You can access it at
    If you want to access the a specific bug say (bug# 3810459) you need to prefix it with "cf-" like so,
    You can read more about this transition at the following blog post:
  3. Aaron Neff
    Hi Piyush,

    I believe Tom's point is: Adobe should correct the links so that they point to

  4. Vamseekrishna Nanneboina
    Hi Aaron/Tom

    All the bugbase links would eventually redirect to The team that built the tracker application is currently working on this.

    We will see if we can edit this document to have the links point to tracker.

  5. Saurav Ghosh
    Hi Tom and Aaron,

    The bug links now point to the right locations instead of the bugbase ones. Sorry for all the confusion.

  6. bped
    WARNING: this update ruins cftextarea on colfusion 11. The code starts referencing CKEditor, but colfusion 11 uses FCKEditor.
  7. charlie arehart
    Yep, and I can concur that it happens (the mistaken reference to ckeditor) even on confirming that the update applied with no errors.

    Specifically it's that the HTML which CF generates refers to files like:


    (which don't exit in CF11). These could refer instead to:


    (which do exist in CF11, though the editor_gecko.css does not exist anywhere in CF11.)

    It seems like this is a mistake perhaps related to how CF2016 update 2 did deprecate FCKeditor in favor of CKeditor. But I'm not aware of anything about CF11 which has yet indicated such deprecation, so this change to those other ckeditor files are just not appropriate for 11.

    Can anyone from Adobe confirm?

    And as a workaround, it would seem to work--for someone who has CF2016--to copy the \ColdFusion2016\cfusion\wwwroot\cf_scripts\scripts\ajax\ckeditor folder to the \ColdFusion11\cfusion\wwwroot\CFIDE\scripts\ajax\ckeditor folder.

    The latter folder does already exist in CF11, though with just one file in it (adapters\jquery.js). I have compared that one file to the one in CF2016 and they are the same, for Cf11 u11 and CF2016 u3 and u2).

    I realize copying that would be a hack, since it's done manually and so won't be managed by subsequent CF 11 updates. I don't see any other ready negative impact.

    Anyway, just pointing it out if someone NEEDS to be on CF11 u11 and needs some workaround. (If they do not have CF2016, I do not feel comfortable sharing the ckeditor folder, so please don't ask me to do so. Press Adobe for a solution. Perhaps they will work up a private update in advance of a more public one to address this.)
  8. bped
    Bug filed, about ckeditor issue:

Leave a Comment

Leave this field empty: