Was Chrome uTLS library bug ever fixed in Throne?

[Bartimius100]

You probably heard that Xray had a vulnerability for like 2 years, when in 50% of the cases when chrome was used as uTLS fingerprint it lead to slightly incorrect behavior, unlike the real Chrome browser, which gave away that you were using proxy. This was fixed on the server side (Xray) a few months ago, that I know about.

What I could not find any real or trustworthy information about, is if clients (Throne, Nekobox, V2rayN and so on) also needed to update things on their side (update uTLS library that is used withing client). I tried looking through changelogs for them to see any mention about fixing uTLS, but found nothing.

Option 1 - clients do not need to make any fixes on their side, it was only server (Xray) issue, everything is handled there
Option 2 - the bug with uTLS was also fixed within all the clients but for some reason not mentioned in changelogs...?

I myself moved to Throne after using Nekobox 3.26 for a long time, but I want to understand if I need to also update things on my mom's PC since she's still using Nekobox 3.26 or there was never an issue on the clients' side with uTLS library and it was only about Xray.

[parhelia512]

Don't expect uTLS to behave perfectly consistent with a real browser.
https://sing-box.sagernet.org/configuration/shared/tls/#utls
https://xtls.github.io/en/config/features/browser_dialer.html#background