Images in cfr reports are not displayed with CF 2025

Forum|Forum|21 days ago
July 14, 2026
6 replies
97 views

Images in cfr reports are not displayed with CF 2025, no matter whether I use a relative path, an absolute path, or a file url. They were still displayed in previous CF versions.

Is this a restriction of the developer version I am currently using?

Any help is appreciated.

Correct answer Charlie Arehart

Hey, great news: I've discovered today that yesterday's cf2025 update 11 HAS FIXED this cfr image bug.

I share more about the update (including this news) at my post:

https://www.carehart.org/blog/2026/7/15/coldfusion_updates_released_jul_14_2026

Check out the update for yourself and let us know how it goes.

ornelloAuthor

Participant

I can confirm that Update 11 has fixed the cfr image bug. Thank you very much for keeping me updated and for the detailed post!

Charlie Arehart

Correct answer

Community Expert

Hey, great news: I've discovered today that yesterday's cf2025 update 11 HAS FIXED this cfr image bug.

I share more about the update (including this news) at my post:

https://www.carehart.org/blog/2026/7/15/coldfusion_updates_released_jul_14_2026

Check out the update for yourself and let us know how it goes.

/Charlie (troubleshooter, carehart. org)

Charlie Arehart

Community Expert

No, it's a bug that others have hit as well. Sadly, the tracker ticketing system (tracker.adobe.com) has been down for a couple of weeks. (The site comes up, but tickets cannot be seen or created.) That has been reported to Adobe, yet still we wait.

As such, it's hard to know where things stand on the bug where others reported this issue some cfreport weeks ago. There's no workaround that I know of.

My sense, from digging into things, is that it started with a change in update 8 regarding xml processing, which is affecting cfreport/cfr processing with regard to the internal jasper report process it relies upon (which I found in digging into the class files created for the cfr file). The cf docs indicate a code change needed for xmlparse, but that doesn't help us: again this issue would be about the internal cf code processing of that xml, nothing we can control.

And also not worked around by any of many combination of jvm args that I and others have attempted.

Again, for several days I've wanted to offer this elaboration (and more) in the tracker ticket but I cannot. I leave this here for you, Adobe, and anyone else interested in the matter.

/Charlie (troubleshooter, carehart. org)

ornelloAuthor

Participant

Thanks a lot for this useful information! This bug is very annoying because we have many reports that are unusable without images. Unfortunately we can’t revert to update 7 because update 8 has fixed another critical issue.

Seems like we have to wait subscribing to CF 2025 until this bug is fixed. tracker.adobe.com is running for me. Do you have an issue number so I can check the progress?

Charlie Arehart

Community Expert

Tracker is not working. You missed what I said, clarifying that, “The site comes up, but tickets cannot be seen or created. “

As such, I can’t find what the ticket id was where someone previously raised the issue...and sadly the search feature here is not finding it. Perhaps someone else will share it.

/Charlie (troubleshooter, carehart. org)

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.