Thank you everyone for your tests and your feedback!
The updates are live now: https://xcp-ng.org/blog/2026/03/26/march-2026-security-updates-2-for-xcp-ng-8-3-lts/
Thank you everyone for your tests and your feedback!
The updates are live now: https://xcp-ng.org/blog/2026/03/26/march-2026-security-updates-2-for-xcp-ng-8-3-lts/
A new security vulnerability has been detected and fixed for xen.
This was introduced by an upstream commit, and detected before the Xen Project did any new release. Therefore this does not impact any upstream release, and there is no Xen Security Advisory this time. But that change was backported into XCP-ng xen package, therefore XCP-ng is impacted.
xen: Fix a security issue where insufficient memory sanitization during guest creation can lead to information leakage from previous guests and potential privilege escalationyum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates
yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates
reboot
The usual update rules apply: pool coordinator first, etc.
xen: 4.17.6-5.2.xcpng8.3Normal use and anything else you want to test.
~2 days
@acebmxer I invite you to open a ticket through the support ticketing system.
I do not connect remotely myself and I am also unable to provide support for Xen-Orchestra.
@acebmxer Hello,
What you're describing sounds more like an RPU issue with Xen-Orchestra than a problem related to XCP-ng updates. But I could be wrong 
However, since these updates affect Xen, a reboot was clearly indicated in our procedure. So a simple restart of the toolstack isn't enough. You did the right thing by rebooting afterward.
Are you using XO Appliance or from source?
If it's XO Appliance, you can open a ticket to ask for help analyzing the situation and see if anything in the logs or configuration explains this behavior.
If it's from source, for the same issue, I would suggest you start a separate thread on the forum so other users can help you with the analysis 
In any case, it's great if your pool is working in the end 
An update for ipmitool has just been released, incorporating a fix for the issue you were experiencing: https://xcp-ng.org/blog/2026/03/19/march-2026-security-updates-for-xcp-ng-8-3-lts/
Thank you everyone for your tests and your feedback!
The updates are live now: https://xcp-ng.org/blog/2026/03/19/march-2026-security-updates-for-xcp-ng-8-3-lts/
So, it seems not an easy task downgrading due to dependencies. -Fixed some, but more coming up..
Anyway, thanks for replying @yann. I will put it to rest and just wait a bit...
Downgrading just ipmitool should not cause dependency issues. Maybe you tried to apply my original suggestion of downgrading xcp-ng-xapi-plugins?
HI @andrew,
Thanks for the report. Would you mind opening an issue in https://gitlab.com/xen-project/xen-guest-agent/-/work_items?