# CVE-2025-1390: pam_cap: Fix potential configuration parsing error

> Attackers can achieve local privilege escalation by exploiting a parsing error in the pam_cap module when capability.conf is configured.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Feb 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-56916, AZL-57034, BELL-CVE-2025-1390, DEBIAN-CVE-2025-1390, ECHO-593e-d2f2-f6da, GHSA-cq92-4vj3-mcq8, MGASA-2025-0082, OESA-2025-1243, UBUNTU-CVE-2025-1390, USN-7287-1

## What is CVE-2025-1390?

CVE-2025-1390 is a medium-severity vulnerability in OpenAnolis Anolis OS, published on 18 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-1390?


## How do I fix CVE-2025-1390?

Apply the vendor's patch.

## Is CVE-2025-1390 being exploited?

There is no known exploitation of CVE-2025-1390 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1390 and fix it if it is affected.

What it is: CVE-2025-1390 is a medium-severity vulnerability in OpenAnolis Anolis OS, published on 18 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1390 in the wild and no public exploit code.

Affected product: OpenAnolis Anolis OS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1390/ (Markdown: https://insights.sbomify.com/CVE-2025-1390/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1390
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1390
- OSV: https://osv.dev/vulnerability/CVE-2025-1390

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1390/
Summaries are generated and may contain mistakes; the official description above is the record.