Does Adobe have a timeline for providing a hotfix for TomCat 7.0.70

Joe, the news is better than what you think--and than Priyank let on.

First, to be clear, it is NOT true that "we never received the update to Tomcat" since "the original post occurred" in 2016. There have indeed been CF11 updates which HAVE updated the Tomcat embedded within CF since then. Multiple times, in fact. The last was update 15, in Sep 2018, whose technote​​​ indicates that it updated Tomcat "from version 7.0.85 to 7.0.90". That is beyond the 7.0.70 you are concerned about from 2016. (And update 12 in Apr 2017 had upgraded it to 7.0.75.)

If you still see Tomcat 7.070 reported in your CF admin (settings summary page) or otherwise, then it would seem just that you have not updated your CF11. You might want to check the CF update level (also reported on that CF admin setting summary, at the top of the report).

That said, Priyank's main point was that support for CF11 formally ended in April (there was one "extra" update in June, which was unusual). They have been clear for almost a year in various posts here and in the CF portal (coldfusion.adobe.com) that CF11's end of life was coming.

(And if you may have wondered how you could know if any CF11 update did update Tomcat, each update's technote is linked to here: ColdFusion 11 updates​. Note that that page itself doesn't always list if a given update did update Tomcat. Its mention of update 15 does not indicate that, but its technote linked to there does. And to get the answer to your question here, I just looked at each, starting from 19 backward, searching within them for "tomcat".)

Finally, while you don't ask about Tomcat 8 with respect CF11, someone else may wonder: Adobe did not ever update CF11 to embed Tomcat 8. That was done only in CF2016 (and then CF2018 embedded Tomcat 9). And FWIW, the last CF2016 update to mention a Tomcat update was update 7, also in Sep 2018, which upgraded tomcat "from 8.5.28 to 8.5.32", which again is well above the 8.0.36 you were concerned about. So it seems you;d be set for that if you updated your CF2016.

Let us know if this satisfies your concern.

All that said, Adobe is indeed behind a bit again on Tomcat updates. And as Priyank mentioned there is an update for CF2016 (and 2018) due that will address that.