Categories

  • All news regarding Xen and XCP-ng ecosystem

    146 Topics
    5k Posts
    gduperreyG
    We have just released security updates for xen and blktap. Full details are available on the blog: https://xcp-ng.org/blog/2026/10/13/october-2026-security-updates-2-for-xcp-ng-8-3-lts/
  • Everything related to the virtualization platform

    1k Topics
    16k Posts
    D
    @Tristis-Oris said: Since I'm the happy owner of this controller, if there's no urgent solution, then tell me which models are definitely compatible with 8.3? The Adaptec ASR-71605 was released in 2012, that's 14 years old. I'd use https://hcl.xenserver.com/search/?type=storagecontrollers&support_status=supported&page=1 to find compatible controllers if you need help. But yeah... 14 year old controller...
  • 3k Topics
    29k Posts
    D
    It's time to update your node.js on your XO instances. Updates are now available for the 26.x, 24.x, 22.x Node.js release lines for the following issues. This security release includes the following dependency updates to address public vulnerabilities: c-ares on 26.x, 24.x, 22.x ca-cert (eMudhra Intermediate CA Compromise) on 26.x, 24.x, 22.x OpenSSL on 24.x, 22.x SQLite on 22.x Undici on 26.x, 24.x, 22.x dns.resolve truncates names containing NUL char (CVE-2026-105482) - (high) This vulnerability affects Node.js 26.x, 24.x, and 22.x. Thank you, to hasanfleyah for reporting this vulnerability and thank you jasnell for fixing it. TLS certificate hostname bypass when the IP is written fullwidth digits (CVE-2026-105483) - (high) This vulnerability affects Node.js 26.x and 24.x. Thank you, to hasanfleyah for reporting this vulnerability and thank you jasnell for fixing it. TLS certificate hostname bypass when the host loosely resolves to an IP address (CVE-2026-106069) - (high) This vulnerability affects Node.js 26.x, 24.x, and 22.x. Thank you, to anagnorisis2peripeteia for reporting this vulnerability and thank you mcollina for fixing it. Node.js Brotli decoder out-of-bounds write permits remote code execution (CVE-2026-111497) - (high) A flaw in Node.js can cause Node.js Brotli decoder out-of-bounds write permits remote code execution. This vulnerability affects Node.js 26.x, 24.x, and 22.x. Thank you, to mcollina for reporting this vulnerability and thank you aduh95 for fixing it. Keep-alive socket process a response that was written before the request was sent (CVE-2026-105481) - (medium) This vulnerability affects Node.js 26.x, 24.x, and 22.x. Thank you, to hasanfleyah for reporting this vulnerability and thank you jasnell for fixing it. Improper certificate validation for non-canonical IPv4 hostnames allows DNS SANs to authenticate IP endpoints (CVE-2026-106072) - (medium) This vulnerability affects Node.js 26.x, 24.x, and 22.x. Thank you, to br41ny for reporting this vulnerability and thank you mcollina for fixing it. crypto.randomUUID() and randomInt() entropy caches are saved into user-land startup snapshots and SEAs, so every process repeats the same values (CVE-2026-106074) - (medium) This vulnerability affects Node.js 26.x, 24.x, and 22.x. Thank you, to gesposito for reporting this vulnerability and thank you panva for fixing it. Node.js ZipFile returns attacker-controlled prefix bytes after failed ZIP header validation (CVE-2026-106070) - (low) This vulnerability affects Node.js 26.x. Thank you, to startimeash for reporting this vulnerability and thank you mcollina for fixing it. Permission Model filesystem over-grant via wildcard radix lookup (CVE-2026-106071) - (low) This vulnerability affects Node.js 26.x. Thank you, to malikhamzaiqbal for reporting this vulnerability and thank you jasnell for fixing it. Permission Model bypass with fs.realpathSync (CVE-2026-106073) - (low) This vulnerability affects Node.js 26.x, 24.x, and 22.x. Thank you, to 0xoroot for reporting this vulnerability and thank you RafaelGSS for fixing it. Downloads and release details Node.js v22.23.4 Node.js v24.22.1 Node.js v26.12.1 Summary The Node.js project will release new versions of the 26.x, 24.x, 22.x releases lines on or shortly after, Wednesday, October 21, 2026 in order to address security vulnerabilities. The highest severity issue fixed in this release is HIGH. Impact The highest severity issue fixed in the 26.x release line is HIGH. The highest severity issue fixed in the 24.x release line is HIGH. The highest severity issue fixed in the 22.x release line is HIGH. https://nodejs.org/en/blog/vulnerability/october-2026-security-releases
  • Our hyperconverged storage solution

    55 Topics
    827 Posts
    C
    @poddingue Hi, we have a ticket at Vates regarding this. (Ticket#7765809)
  • 37 Topics
    137 Posts
    S
    @jqueiroz said: Bom dia a todos, Estou com um problema em uma VM, ela está ligando/desligando sozinha, repetidamente. Não encontro nenhuma mensagem de erro explicando o motivo. Alguém pode me dar alguma dica sobre como solucionar isso? Uso o XCP-NG 8.0 em um cluster de dois servidores HP Proliant DL-360, com o HA-Lizard. Tudo vinha funcionando bem até alguns dias atrás, quando houve uma queda de energia no datacenter da localidade. Tenho o mesmo arranjo de VMs/servidores em mais seis localidades, nenhuma apresenta esse problema. Analisar esse comportamento instável do cluster é quase como prever resultados complexos, parecendo a análise de riscos que a malta faz ao dar palpites no https://mostbetbrasil.lat. Grato. Como o problema começou depois da queda de energia e só acontece nessa localidade, eu começaria verificando os logs do XCP-ng e do HA-Lizard para entender quem está disparando os reinícios. Pode ser alguma política de HA tentando recuperar a VM repetidamente, algum problema de armazenamento ou até inconsistência no estado do host após a interrupção. Também vale conferir o estado do pool e os logs do Xen Orchestra, se estiver usando. Se possível, desative temporariamente a automação de recuperação dessa VM, com cuidado para não comprometer a disponibilidade, e veja se ela continua reiniciando sozinha. Isso ajuda a isolar a causa.