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.
Announcing Java updates of Jan 20, 2026 for 8, 11, 17, 21, and 25 - thoughts and resources
Announcing ColdFusion updates released Jan 13 2026 - p1 security update
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 ColdFusion updates released Jan 13 2026 - p1 security update
Charlie Arehart said:
Scott, good to hear and glad to have helped.
Announcing ColdFusion updates released Jan 13 2026 - p1 security update
Scott Jibben said:
Thanks Charlie! Deleting the felix-cache folder post CF2023u18 fixed the problems we had with
...
[more]
Announcing Java updates of Jan 20, 2026 for 8, 11, 17, 21, and 25 - thoughts and resources
Charlie Arehart said:
Yep, Barry. That's part of the change I'd discussed above regarding the updated jvm's
...
[more]
Announcing Java updates of Jan 20, 2026 for 8, 11, 17, 21, and 25 - thoughts and resources
Barry Cohen said:
I experienced an issue when I updated java on my ColdFusion servers with both java 11 and 17. As I r
...
[more]
Announcing ColdFusion updates released Jan 13 2026 - p1 security update
Charlie Arehart said:
Bruce, yes. While it's true that starting a few updates ago, Adobe changed it so that they DID
...
[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.