# Regarding the security notice

**URL:** <https://forum.gl-inet.com/t/regarding-the-security-notice/73057>\
**Category:** Router\
**Created:** [November 21, 2026, 11:06am UTC](https://forum.gl-inet.com/t/regarding-the-security-notice/73057 "2026-11-21T11:06:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![rthco](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/rthco/32/20980_2.png) [@rthco](https://forum.gl-inet.com/u/rthco)\
**Post date:** [November 21, 2026, 11:07am UTC](https://forum.gl-inet.com/t/regarding-the-security-notice/73057/2 "2026-11-21T11:07:51Z")

</div>

You are not alone:

> [@2026-11-20: GL.iNet Security Notice - GoodCloud / KVM / Routers](https://forum.gl-inet.com/t/2026-11-20-gl-inet-security-notice-goodcloud-kvm-routers/73056/11):
>
> @bruce @will.qiu - I'm going to post the same reply as on reddit.. This vague notice is NOT the way to do things. Can you publicly post the root issue, detection & mitigation process asap please? Like right here, right now please? This isn't the type of thing to keep gated behind someone checking or receiving an email. That is not how CVE and security disclosure is done for an active threat already being exploited. We should be able to start detection and mitigation immediately. Has GL registe…

---

_[View the full topic](https://forum.gl-inet.com/t/regarding-the-security-notice/73057)._
