Adobe ColdFusion 2021 reached the end of extended support on November 10, 2026. If you still run it, you're not in trouble for missing the date. You're in a new operating mode, and it has its own rules: no fix is coming, so your job is to limit what a bug can cost you while you upgrade.
We migrated several production applications to ColdFusion 2025 in 2026. Our earlier post on ColdFusion 2021 end of support covers the basics: confirm your build, close the Administrator, put a firewall rule in front of public apps. Here's what we'd add in the first week on an unsupported server.
1. Write the risk down and give it an owner. One page. List the servers, the data they hold, the controls in front of them, and the date you leave. Get a named person to sign it. Auditors and customer security reviews will ask about an unsupported runtime. A signed page with an exit date is a much better answer than "we know."
2. Read every new Adobe ColdFusion bulletin as if it names your server. Adobe still fixes bugs in ColdFusion 2023 and 2025. Your 2021 server won't appear on those bulletins, and that tells you nothing about whether it has the bug. Assume it does. For each bulletin, ask one question: which of our controls stops this class of attack? If the answer is "none," that's this week's work.
3. Shrink the blast radius. Blast radius is what an attacker can reach after they get into one server. You can't patch the hole, so limit what's behind it. Run ColdFusion under a service account with only the rights it needs. Cut the database login down to the tables the app uses. Block outbound traffic the app doesn't need. Delete data sources and sample apps nobody uses.
4. Send the logs somewhere else, and have someone read them. Ship the web server, ColdFusion, and firewall logs off the box. Alert on three things: requests to the Administrator path, new files in the web root, and new scheduled tasks. On older servers we usually find the logs exist and nobody has looked at them in a year.
5. Time a full restore. Restore the server and its database to a clean machine and time it. A backup you've never restored isn't a recovery plan. On a server that can't be patched, the restore is how you recover, so you need to know how long it takes.
6. Stand up a ColdFusion 2025 test server now. Don't wait for the project to be approved. Install ColdFusion 2025 on a test machine, point a copy of the app at it, and write down what breaks. A short list of real failures gets a budget faster than a risk memo does, and in our experience the list is shorter than people fear. Our ColdFusion 2025 migration checklist covers what to test.
None of this replaces the upgrade. It buys you a safer few months to do it properly. If you want help with the controls while the server stays put, that's what ColdFusion security remediation is for.

