VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

systemd: vulnerability history, versions and safety

systemd is a package in the OSS-Fuzz ecosystem. Vulert records 23 vulnerabilities for it across 4 releases, from Jun 2020 to Apr 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
23 vulnerabilities recorded H8 M15
i
1 with no fix published

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

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

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all systemd vulnerabilities

Vulert verdict on systemd i

Updated on 23 Oct 2026

Careful: one of the 23 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 23 vulnerabilities on record across 2 years, none in the last year.

What to do: Plan around the 1 vulnerability 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 23 over 2 years · 0 in the last year i
  • Latest disclosure 14 Apr 2023 i
  • Highest CVSS n/a i
  • With no published fix 1 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 systemd, 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.

i
Version Vulert vulnerabilities Fix published Details
v253 M1 No Details →
v253-rc3 M1 No Details →
v253-rc2 M1 No Details →
v253-rc1 M1 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 4
  • 2021 5
  • 2022 4
  • 2023 10

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

03 Vulnerabilities

Recorded vulnerabilities for systemd

The 5 most severe of 23 vulnerabilities recorded for this package

Search all 23 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
UNKNOWN READ Vulnerability in systemd N/A medium 212bd73c788c464c2e19596a102feed848cb78fa 13 Jan 2021
Heap-buffer-overflow in dhcp6_option_parse_status in systemd N/A medium 84452783b8bcc44e0dbb7fa6ddc6dad8c064bdfe 13 Jan 2021
Use-of-uninitialized-value in rename_process in systemd N/A medium No fix published 28 Feb 2023
Heap-use-after-free in condition_free_list_type in systemd N/A high 7bb55ed099f611ec7077db69684a6cb93d42dc70 01 Jul 2020
Heap-use-after-free in condition_free_list_type in systemd N/A high 7bb55ed099f611ec7077db69684a6cb93d42dc70 30 Jun 2020

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 systemd

Is systemd safe to use?

Vulert records 23 vulnerabilities for systemd in OSS-Fuzz: 0 critical, 8 high, 15 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does systemd have?

23 vulnerabilities are recorded for systemd in the OSS-Fuzz ecosystem: 0 critical, 8 high, 15 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new systemd vulnerabilities disclosed?

0 vulnerabilities were recorded for systemd in the last 12 months, and the oldest entry in this database dates to 30 Jun 2020. 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 systemd 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 systemd for upcoming vulnerabilities?

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