Vulnerability Database · Debian · Package report

libreswan: vulnerability history, versions and safety

libreswan is a package in the Debian ecosystem. Vulert records 24 vulnerabilities for it across 27 releases, from Sep 2018 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
24 vulnerabilities recorded U24
i
10 with no fix published

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

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

Most recent disclosure 27 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on libreswan i

Updated on 22 Oct 2026

Careful: 10 of the 24 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 24 vulnerabilities on record across 7 years, 4 in the last year.

What to do: Plan around the 10 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 24 over 7 years · 4 in the last year i
  • Latest disclosure 27 Jul 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 10 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 libreswan, 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 27 of 27 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2019 4
  • 2020 2
  • 2022 3
  • 2023 7
  • 2024 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for libreswan

The 5 most severe of 24 vulnerabilities recorded for this package

Search all 24 in the database →

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Questions

About libreswan

Is libreswan safe to use?

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

How many vulnerabilities does libreswan have?

24 vulnerabilities are recorded for libreswan in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 24 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 libreswan vulnerabilities disclosed?

4 vulnerabilities were recorded for libreswan in the last 12 months, and the oldest entry in this database dates to 06 Sep 2018. 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 libreswan 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 libreswan for upcoming vulnerabilities?

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