| Re: Urgent: GhostLock (CVE-2026-43499) on OpenVZ 7 Where is the patch for WebPros / SolusVM users? [message #53901 is a reply to message #53900] |
Thu, 23 July 2026 09:32   |
HHawk
Messages: 43 Registered: September 2017 Location: Europe
|
Member |
|
|
It is deeply disappointing to see the current state of the OpenVZ project. Updates for OpenVZ 7 have become extremely scarce, while OpenVZ 9 still does not appear to be developing into a maintained and dependable successor. Much of the project now feels outdated or effectively abandoned.
The lack of visible action following the disclosure of GhostLock (CVE-2026-43499) in early July 2026 has made the situation even more concerning. Regardless of the exact exposure of individual OpenVZ kernels, long-standing users deserve timely communication, clear security guidance and evidence that the platform is still being actively maintained. Unfortunately, we have seen very little of that.
A relevant detail is that we operate two separate companies. One uses OpenVZ-based solutions, while the other uses commercial Virtuozzo products for customers who are prepared to pay more for that platform. Virtuozzo may not be aware that both environments ultimately belong to us.
It may be assumed that organisations still using OpenVZ will eventually migrate to the paid Virtuozzo platform. In our case, however, the opposite is happening. Trust must be earned and maintained before customers will consider investing further in a commercial product. After years of uncertainty, delayed development, limited communication and unfulfilled expectations surrounding OpenVZ, that trust has largely disappeared.
We have therefore already started migrating our infrastructure to Proxmox. This is not a decision we have taken lightly. We have been using OpenVZ for more than twenty years, and it has been an important part of our infrastructure for a very long time. It has been a great journey, but we can no longer continue relying on a platform whose future and security maintenance remain so unclear.
Virtuozzo may not consider the loss of our OpenVZ and commercial Virtuozzo deployments significant, but it matters to us. We are tired of repeatedly being left waiting, receiving little meaningful information and being given the impression that improvements are coming while very little actually changes.
It is genuinely unfortunate that our journey with OpenVZ and Virtuozzo has to end this way. However, given the current state of the project and the lack of confidence in its future, migrating to Proxmox has become the only responsible choice for our companies and our customers.
|
|
|
|