Libcap
5 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Libcap, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Libcap CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 1 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 1 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 5 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High1
- Medium3
- Low1
Latest CVEs
The 5 most recently published vulnerabilities affecting Libcap.
- CVE-2026-4878Libcap: libcap: privilege escalation via toctou race condition in cap_set_file()6.7
- CVE-2025-1390pam_cap: Fix potential configuration parsing error6.1
- CVE-2023-2603A vulnerability was found in libcap. This issue occurs in the _libcap_strdup() function and can lead to an integer overflow if the input string is close to 4GiB.7.8
- CVE-2023-2602A vulnerability was found in the pthread_create() function in libcap. This issue may allow a malicious actor to use cause __real_pthread_create() to return an error, which can exhaust the process m...3.3
- CVE-2011-4099The capsh program in libcap before 2.22 does not change the current working directory when the --chroot option is specified, which allows local users to bypass the chroot restrictions via unspecifi...4.6
Product grouping is registry-driven, with AI assist and human review. How it works