VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

xen: vulnerability history, versions and safety

xen is a package in the Debian ecosystem. Vulert records 43 vulnerabilities for it across 26 releases, from Nov -0001 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
43 vulnerabilities recorded U43
i
14 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
14 in the last 12 months

Most recent disclosure 13 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all xen vulnerabilities

Vulert verdict on xen i

Updated on 23 Oct 2026

Careful: 14 of the 43 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 43 vulnerabilities on record across 2026 years, 14 in the last year.

What to do: Plan around the 14 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 43 over 2026 years · 14 in the last year i
  • Latest disclosure 13 Oct 2026 i
  • Highest CVSS 4.3 i
  • With no published fix 14 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for xen, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 26 of 26 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2022 1
  • 2023 4
  • 2024 23
  • 2025 1
  • 2026 13

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 14 of the 43 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for xen

The 5 most severe of 43 vulnerabilities recorded for this package

Search all 43 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Memory Scrubbing Vulnerability in Xen Package: CVE-2026-79603 4.3 medium No fix published 08 Sep 2026
Critical PCI Device Vulnerability in Xen Package: CVE-2026-79602 N/A unrated No fix published 08 Sep 2026
PCI Device Cleanup Vulnerability in Xen Package N/A unrated No fix published 08 Sep 2026
Critical Logical Error in Xen Package: XSA-407 and XSA-434 Vulnerability N/A unrated 4.17.5+23-ga4e5191dc0-1 16 May 2024
Critical Vulnerability in Xen Package: CVE-2026-79611 N/A unrated No fix published 13 Oct 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About xen

Is xen safe to use?

Vulert records 43 vulnerabilities for xen in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 43 not yet rated. 14 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does xen have?

43 vulnerabilities are recorded for xen in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 43 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new xen vulnerabilities disclosed?

14 vulnerabilities were recorded for xen in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of xen are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor xen for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the xen version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.