https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T05:46:54.866724+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2022-06183 bdu:2022-06183 2026-10-03T05:46:54.886212+00:00 bdu:2022-06183 https://cve.radiocsirt.org/vuln/certfr-2020-avi-824 certfr-2020-avi-824 — De multiples vulnérabilités ont été découvertes dans Xen. Elles permettent à un attaquant de provoquer un déni de servi… 2026-10-03T05:46:54.886256+00:00 certfr-2020-avi-824 https://cve.radiocsirt.org/vuln/euvd-2026-47336 EUVD-2026-47336 2026-10-03T05:46:54.886275+00:00 EUVD-2026-47336 https://cve.radiocsirt.org/vuln/fkie_cve-2020-29481 fkie_cve-2020-29481 2026-10-03T05:46:54.886287+00:00

An issue was discovered in Xen through 4.14.x. Access rights of Xenstore nodes are per domid. Unfortunately, existing granted access rights are not removed when a domain is being destroyed. This means that a new domain created with the same domid will inherit the access rights to Xenstore nodes from the previous domain(s) with the same domid. Because all Xenstore entries of a guest below /local/domain/<domid> are being deleted by Xen tools when a guest is destroyed, only Xenstore entries of other guests still running are affected. For example, a newly created guest domain might be able to read sensitive information that had belonged to a previously existing guest domain. Both Xenstore implementations (C and Ocaml) are vulnerable.

 https://cve.radiocsirt.org/vuln/ghsa-vcqm-hqq4-5mxm GHSA-vcqm-hqq4-5mxm 2026-10-03T05:46:54.886319+00:00

An issue was discovered in Xen through 4.14.x. Access rights of Xenstore nodes are per domid. Unfortunately, existing granted access rights are not removed when a domain is being destroyed. This means that a new domain created with the same domid will inherit the access rights to Xenstore nodes from the previous domain(s) with the same domid. Because all Xenstore entries of a guest below /local/domain/<domid> are being deleted by Xen tools when a guest is destroyed, only Xenstore entries of other guests still running are affected. For example, a newly created guest domain might be able to read sensitive information that had belonged to a previously existing guest domain. Both Xenstore implementations (C and Ocaml) are vulnerable.

 https://cve.radiocsirt.org/vuln/gsd-2020-29481 gsd-2020-29481 2026-10-03T05:46:54.886339+00:00 gsd-2020-29481 https://cve.radiocsirt.org/vuln/opensuse-su-2020:2313-1 openSUSE-SU-2020:2313-1 — Security update for xen 2026-10-03T05:46:54.886350+00:00

Security update for xen

 https://cve.radiocsirt.org/vuln/suse-su-2020:14578-1 SUSE-SU-2020:14578-1 — Security update for xen 2026-10-03T05:46:54.886368+00:00

Security update for xen

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-29481 UBUNTU-CVE-2020-29481 2026-10-03T05:46:54.886384+00:00

Affected: Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen, Ubuntu:20.04:LTS: xen

An issue was discovered in Xen through 4.14.x. Access rights of Xenstore nodes are per domid. Unfortunately, existing granted access rights are not removed when a domain is being destroyed. This means that a new domain created with the same domid will inherit the access rights to Xenstore nodes from the previous domain(s) with the same domid. Because all Xenstore entries of a guest below /local/domain/<domid> are being deleted by Xen tools when a guest is destroyed, only Xenstore entries of other guests still running are affected. For example, a newly created guest domain might be able to read sensitive information that had belonged to a previously existing guest domain. Both Xenstore implementations (C and Ocaml) are vulnerable.