Announcing CF update released Jul 14 2023 - a second priority 1 security update in one week
For more on the update, and some additional thoughts, read on.
For more on the update, and some additional thoughts, read on.
One explanation and solution for when applying CF updates uninstalls new packages unexpectedly
Announcing ColdFusion updates released Dec 9 2025 - p1 security update and more
Reminder that CF2021 is end-of-life as of Monday Nov 10 2025
Announcing Java updates of Oct 21, 2025 for 8, 11, 17, 21, and 25 - thoughts and resources
Announcing ColdFusion updates released Sep 9 2025 - p1 security update
When and how to upgrade CF web server connector, easier in recent CF releases
wei said:
Thank you for your detailed and clear explanation, which solved many problems
One explanation and solution for when applying CF updates uninstalls new packages unexpectedly
Charlie Arehart said:
Branden, if I could help you solve whatever is amiss, would you be open to having a half hour engage
...
[more]
One explanation and solution for when applying CF updates uninstalls new packages unexpectedly
Branden P de Buhr said:
On my work / corp laptop, I run my dev environment. Which was running previously on cf 2023 u
...
[more]
Announcing ColdFusion updates released Dec 9 2025 - p1 security update and more
Charlie Arehart said:
Tim, any thoughts on what I'd shared? Did you confirm things work as I proposed? Did
...
[more]
Announcing ColdFusion updates released Dec 9 2025 - p1 security update and more
Charlie Arehart said:
Tim, that's incorrect.
...
CAN use that JVM arg with CF2025 and it IS honore
...
[more]


I will note that while that post indicates that "There is currently no mitigation", that may not be the final/complete answer. Note how it refers to the _cfclient querystring, and notice that in my first post last week (on the Jul 11 CF update), I did point out how my March blog post on the previous CF update discussed ways to BLOCK ALL REQUESTS using that _cfclient querystring. I also elaborate there on what it's about, how one can determine if they may have any legit use of it (most do not), and much more. See https://www.carehart...
As I've said elsewhere, it's just not clear how many of the recently closed vulns DO work based on the _cfclient querystring. That post is about all we have to go on, as I've not seen any others. While those on cf2018 and above can apply these fixes to address what Adobe has found, it's just not clear (for now) what those on cf2016 can or should do, other than block requests with that querystring.