Vulnerability Database · Debian · libcap2 · Version

libcap2 1:2.44-1

1:2.44-1 is affected by 6 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 0 High 0 Medium 0 Low 0 Unrated 6

All libcap2 versions & vulnerabilities → Search the database for this package →

Database updated 23/Oct/2026

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.

Scan your app free →

01 Vulnerabilities affecting this version

libcap2 1:2.44-1 vulnerabilities

6 vulnerabilities cover libcap2 1:2.44-1. Open the full list in the database.

Vulnerability	Severity	Fixed version	Disclosed
Critical Vulnerability in libcap2: CVE-2026-4878 Exposes Security Risks	N/A unrated	No fix published	06 Apr 2026
Critical Security Update for libcap2: Addressing Multiple Vulnerabilities	N/A unrated	1:2.44-1+deb11u1	26 Mar 2025
Local Privilege Escalation Vulnerability in libcap2 PAM Module	N/A unrated	1:2.44-1+deb11u1	18 Feb 2025
Local Privilege Escalation Vulnerability in libcap2 PAM Module	N/A unrated	1:2.44-1+deb11u1	18 Feb 2025
Integer Overflow Vulnerability in libcap2: Potential for Exploitation	N/A unrated	1:2.44-1+deb11u1	06 Jun 2023
Critical Vulnerability in libcap2: Memory Exhaustion via pthread_create()	N/A unrated	1:2.44-1+deb11u1	06 Jun 2023

Looking for another version, or everything Vulert holds for libcap2?

All versions → Full vulnerability list →

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 1:2.44-1

Is libcap2 1:2.44-1 vulnerable?

Yes. 6 vulnerabilities in the Vulert database cover libcap2 1:2.44-1: 0 critical, 0 high, 0 medium and 0 low, plus 6 not yet rated. Each entry above names the fixed version to move to.

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.