Vulnerability Database · Debian · Package report

libcrypt-dsa-perl: vulnerability history, versions and safety

libcrypt-dsa-perl is a package in the Debian ecosystem. Vulert records 6 vulnerabilities for it across 5 releases, from Oct 2011 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
6 vulnerabilities recorded U6
i
4 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 05 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on libcrypt-dsa-perl i

Updated on 23 Oct 2026

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

What to do: Plan around the 4 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 6 over 14 years · 4 in the last year i
  • Latest disclosure 05 Jul 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 4 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 libcrypt-dsa-perl, 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
1.21-1 U2 No Details →
1.20-1 U2 No Details →
1.19-1 U4 No Details →
1.17-5 U4 No Details →
1.17-4 U4 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2011 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for libcrypt-dsa-perl

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 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: 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 libcrypt-dsa-perl

Is libcrypt-dsa-perl safe to use?

Vulert records 6 vulnerabilities for libcrypt-dsa-perl in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 6 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libcrypt-dsa-perl have?

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

4 vulnerabilities were recorded for libcrypt-dsa-perl in the last 12 months, and the oldest entry in this database dates to 10 Oct 2011. 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 libcrypt-dsa-perl 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 libcrypt-dsa-perl for upcoming vulnerabilities?

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