VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libcap2: vulnerability history, versions and safety

libcap2 is a package in the Debian ecosystem. Vulert records 8 vulnerabilities for it across 29 releases, from Feb 2014 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded U8
i
1 with no fix published

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

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

Most recent disclosure 06 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libcap2 vulnerabilities

Vulert verdict on libcap2 i

Updated on 23 Oct 2026

Careful: one of the 8 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 8 vulnerabilities on record across 12 years, 1 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 8 over 12 years · 1 in the last year i
  • Latest disclosure 06 Apr 2026 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 libcap2, 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 29 of 29 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 2
  • 2023 2
  • 2025 3
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for libcap2

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2011-4099: Chroot Bypass in libcap2 N/A unrated 1:2.22-1 08 Feb 2014
Local Privilege Escalation Vulnerability in libcap2 PAM Module N/A unrated 1:2.44-1+deb11u1 18 Feb 2025
Critical Security Update for libcap2: Addressing Multiple Vulnerabilities N/A unrated 1:2.44-1+deb11u1 26 Mar 2025
Local Privilege Escalation in libcap2: Chroot Bypass Vulnerability N/A unrated 1:2.22-1 08 Feb 2014
Critical Vulnerability in libcap2: Memory Exhaustion via pthread_create() N/A unrated 1:2.44-1+deb11u1 06 Jun 2023

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 libcap2

Is libcap2 safe to use?

Vulert records 8 vulnerabilities for libcap2 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 8 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does libcap2 have?

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

1 vulnerability was recorded for libcap2 in the last 12 months, and the oldest entry in this database dates to 08 Feb 2014. 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 libcap2 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 libcap2 for upcoming vulnerabilities?

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