A vulnerability was found in libcap.
Noroxi assessment
Priority: Monitor (action score 31/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.57% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: libcap (AlmaLinux:8) 2.48-5.el8_8; libcap-devel (AlmaLinux:8) 2.48-5.el8_8; libcap (AlmaLinux:9) 2.48-9.el9_2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to libcap (AlmaLinux:8) 2.48-5.el8_8; libcap-devel (AlmaLinux:8) 2.48-5.el8_8; libcap (AlmaLinux:9) 2.48-9.el9_2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A 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.
- Published
- Jun 6, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 46th percentile
- CWE
- CWE-190
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libcap project | libcap | cpe:2.3:a:libcap_project:libcap |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- fedoraproject fedora37
- fedoraproject fedora38
- libcap project libcapbefore 2.69
- redhat enterprise linux8.0
- redhat enterprise linux9.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a libcap
- NAaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | libcap | before 2.48-5.el8_8 | 2.48-5.el8_8 |
| AlmaLinux:8 | libcap-devel | before 2.48-5.el8_8 | 2.48-5.el8_8 |
| AlmaLinux:9 | libcap | before 2.48-9.el9_2 | 2.48-9.el9_2 |
| AlmaLinux:9 | libcap-devel | before 2.48-9.el9_2 | 2.48-9.el9_2 |
| Alpine:v3.15 | libcap | before 2.61-r1 | 2.61-r1 |
| Alpine:v3.16 | libcap | before 2.64-r1 | 2.64-r1 |
| Alpine:v3.17 | libcap | before 2.66-r1 | 2.66-r1 |
| Debian:11 | libcap2 | before 1:2.44-1+deb11u1 | 1:2.44-1+deb11u1 |
| Debian:12 | libcap2 | before 1:2.66-4 | 1:2.66-4 |
| openSUSE:Leap 15.4 | libcap | before 2.26-150000.4.9.1 | 2.26-150000.4.9.1 |
| openSUSE:Leap Micro 5.3 | libcap | before 2.63-150400.3.3.1 | 2.63-150400.3.3.1 |
| Red Hat:enterprise_linux:8::baseos | libcap | before 0:2.48-5.el8_8 | 0:2.48-5.el8_8 |
| Red Hat:enterprise_linux:8::baseos | libcap-debuginfo | before 0:2.48-5.el8_8 | 0:2.48-5.el8_8 |
| Red Hat:enterprise_linux:8::baseos | libcap-debugsource | before 0:2.48-5.el8_8 | 0:2.48-5.el8_8 |
| Red Hat:enterprise_linux:8::baseos | libcap-devel | before 0:2.48-5.el8_8 | 0:2.48-5.el8_8 |
| Red Hat:enterprise_linux:9::appstream | libcap-debuginfo | before 0:2.48-9.el9_2 | 0:2.48-9.el9_2 |
| Red Hat:enterprise_linux:9::appstream | libcap-debugsource | before 0:2.48-9.el9_2 | 0:2.48-9.el9_2 |
| Red Hat:enterprise_linux:9::appstream | libcap-devel | before 0:2.48-9.el9_2 | 0:2.48-9.el9_2 |
| Red Hat:enterprise_linux:9::baseos | libcap | before 0:2.48-9.el9_2 | 0:2.48-9.el9_2 |
| Red Hat:rhel_eus:8.6::baseos | libcap | before 0:2.48-4.el8_6 | 0:2.48-4.el8_6 |
| Red Hat:rhel_eus:8.6::baseos | libcap-debuginfo | before 0:2.48-4.el8_6 | 0:2.48-4.el8_6 |
| Red Hat:rhel_eus:8.6::baseos | libcap-debugsource | before 0:2.48-4.el8_6 | 0:2.48-4.el8_6 |
| Red Hat:rhel_eus:8.6::baseos | libcap-devel | before 0:2.48-4.el8_6 | 0:2.48-4.el8_6 |
| Red Hat:rhel_eus:9.0::appstream | libcap-debuginfo | before 0:2.48-8.el9_0.1 | 0:2.48-8.el9_0.1 |
+7
Same product
libcap project: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-4878Libcap: libcap: privilege escalation via toctou race condition in cap_set_file()28Monitor
- CVE-2023-2602A vulnerability was found in the pthread_create() function in libcap.13Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:libcap | 2.48-5.el8_8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:libcap-devel | 2.48-5.el8_8 · AlmaLinux:8 | Package registry (OSV) |
| alpine:libcap | 2.61-r1 · Alpine:v3.15 | Package registry (OSV) |
| debian:libcap2 | 1:2.66-4 · Debian:12 | Package registry (OSV) |
| opensuse:libcap | 2.63-150400.3.3.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| red hat:libcap | 0:2.48-5.el8_8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libcap-debuginfo | 0:2.48-5.el8_8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libcap-debugsource | 0:2.48-5.el8_8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libcap-devel | 0:2.48-5.el8_8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| rocky linux:libcap | 0:2.48-5.el8_8 · Rocky Linux:8 | Package registry (OSV) |
| suse:libcap | 2.26-14.9.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
| suse:libcap | 2.63-150400.3.3.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2024-11-12 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+524 d
- TodayOct 25, 2026+1236 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0499 · Sep 7, 2023(Multicluster Engine Güvenlik Zafiyeti)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.