# Questions about the critical ThinLinc security issue found on 04-08-2026 **URL:** \ **Category:** Community Support\ **Tags:** security\ **Created:** [8 April 2026 14:14 UTC](https://community.thinlinc.com/t/questions-about-the-critical-thinlinc-security-issue-found-on-04-08-2026/1971 "2026-04-08T14:14:10Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Lucy\_Z](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/lucy_z/32/720_2.png) [@Lucy\_Z](https://community.thinlinc.com/u/Lucy_Z)\ **Post date:** [8 April 2026 14:14 UTC](https://community.thinlinc.com/t/questions-about-the-critical-thinlinc-security-issue-found-on-04-08-2026/1971/1 "2026-04-08T14:14:10Z")
Hi all, I just saw the urgent announcement about the security issue that has been found on Thinlinc servers on 04-08-2026: > [@Urgent: ThinLinc security issue](https://community.thinlinc.com/t/urgent-thinlinc-security-issue/1970): > > A critical security issue has been discovered in the ThinLinc server that allows any user to impersonate any other user, including the root user. This issue affects all versions of ThinLinc. Fixes for all supported versions of ThinLinc will be released at noon UTC 2026-04-22. Users running a version older than ThinLinc 4.15.0 should be prepared to not just apply the fix, but also to do an upgrade to a supported version. There are no known mitigations for this issue. Users should be prepared to… Because that post does not allow replies, I am creating this thread here. I do thank ThinLinc for promptly letting us know about the issue, but because a patch is expected only 14 days from now, I am afraid we need more information than what was provided. For example: 1. what does “allows any user to impersonate any other user” mean exactly? Would the impersonator need to know the real user’s password or can they do so without that? 2. does that affect the security of our servers in what regards non-users? That is, can attackers that are not at all registered as users have access to our servers in any way due to this issue? 3. are there any measures that we can take in the meanwhile to mitigate risks? Thanks for clarifying these topics! ---
**Author:** ![aaron](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/aaron/32/13_2.png) [@aaron](https://community.thinlinc.com/u/aaron)\ **Post date:** [8 April 2026 18:53 UTC](https://community.thinlinc.com/t/questions-about-the-critical-thinlinc-security-issue-found-on-04-08-2026/1971/2 "2026-04-08T18:53:43Z")
Hi @Lucy_Z, The issue relates to existing, authenticated users. So it is only users who are already able to authenticate successfully who would be able to impersonate others. Unfortunately, in the interests of responsible disclosure, we’re unable to divulge much more information at present. The fix will be provided as a point release, so we wanted to give enough notice for people to schedule in a maintenance window for the upgrade. Appreciate your understanding in all of this! ---
**Author:** ![wilsj](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/wilsj/32/554_2.png) [@wilsj](https://community.thinlinc.com/u/wilsj)\ **Post date:** [8 April 2026 19:06 UTC](https://community.thinlinc.com/t/questions-about-the-critical-thinlinc-security-issue-found-on-04-08-2026/1971/3 "2026-04-08T19:06:41Z")
Also note that the issue was discovered during a penetration test. We have not seen any indications of it being used by malicious actors in the wild. ---
**Author:** ![sswirski](https://avatars.discourse-cdn.com/v4/letter/s/f9ae1b/32.png) [@sswirski](https://community.thinlinc.com/u/sswirski)\ **Post date:** [9 April 2026 05:51 UTC](https://community.thinlinc.com/t/questions-about-the-critical-thinlinc-security-issue-found-on-04-08-2026/1971/4 "2026-04-09T05:51:55Z")
> [@aaron](#): > > So it is only users who are already able to authenticate successfully who would be able to impersonate others. Okay, so that sounds like “if I trust my current users and their client machines have not been compromised (no credentials or 2FA tokens leaked), I have nothing to fear at the moment”? ---
**Author:** ![wilsj](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/wilsj/32/554_2.png) [@wilsj](https://community.thinlinc.com/u/wilsj)\ **Post date:** [9 April 2026 06:05 UTC](https://community.thinlinc.com/t/questions-about-the-critical-thinlinc-security-issue-found-on-04-08-2026/1971/5 "2026-04-09T06:05:06Z")
> Okay, so that sounds like “if I trust my current users and their client machines have not been compromised (no credentials or 2FA tokens leaked), I have nothing to fear at the moment”? Yes. That is correct.