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.
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
Announcing Java updates of Jul 15, 2025 for 8, 11, 17, 21, and 24 - thoughts and resources
Announcing ColdFusion updates released July 8 2025 - p1 security update and more
Announcing ColdFusion updates released July 8 2025 - p1 security update and more
Vicki said:
To provide some quick answers:
- I was previously on ColdFusion 2023 Update 14
...
[more]
Announcing ColdFusion updates released July 8 2025 - p1 security update and more
Charlie Arehart said:
Vicki, I have some follow up (it's not clear if you tried things in that demo tool, though
...
[more]
Announcing ColdFusion updates released July 8 2025 - p1 security update and more
Vicki said:
Hi Charlie - yes, ColdFusion 2023 (not 2025), that was a typo. Yes, I deleted the felix-ca
...
[more]
Announcing ColdFusion updates released July 8 2025 - p1 security update and more
Charlie Arehart said:
Oh, and as a follow-up to my reply to Vicki just now, I just confirmed I got the same successful res
...
[more]
Announcing ColdFusion updates released July 8 2025 - p1 security update and more
Charlie Arehart said:
Vicki, I appreciate that you're offering that to help others, but I don't find that to be
...
[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.