We ended up there because committees were afraid to say no to requests adding chinese, japanese or whatever variable names to your favorite compiler. But then they also didn't care about identifiers staying identifiable, which is the goal of TR 39. So many compilers did add "Unicode support" for the language.
Only 3-4 compilers stayed secure in this regard, by either disallowing unicode names, or by using TR39.
What else is a high security riscs? All names, such as path names or user names on OS kernels, like filesystems. Filesystem or user db's with unicode support but without identifier support such as TR39 can also lead to security attacks. Apple once had at least HPFS which did normalization, but the recently gave up, because nobody cared. And Linus still calls garbage in, garbage out valuable. Even if the famous ssh attack used such an homoglyph attack to stay undetected.