EUVD-2025-19056
2025-06-17
[email protected]
7.8
CVSS 3.1
Share
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Lifecycle Timeline
4
Patch Released
Mar 31, 2026 - 21:13 nvd
Patch available
Analysis Generated
Mar 14, 2026 - 22:15 vuln.today
EUVD ID Assigned
Mar 14, 2026 - 22:15 euvd
EUVD-2025-19056
CVE Published
Jun 17, 2025 - 13:15 nvd
HIGH 7.8
Tags
Description
A flaw was found in linux-pam. The module pam_namespace may use access user-controlled paths without proper protection, allowing local users to elevate their privileges to root via multiple symlink attacks and race conditions.
Analysis
A privilege escalation vulnerability in A flaw (CVSS 7.8). High severity vulnerability requiring prompt remediation.
Technical Context
CWE-22 (Path Traversal). CVSS 7.8 indicates high severity. Affects A flaw.
Affected Products
['A flaw']
Remediation
Monitor vendor channels for patch availability.
Priority Score
39
Low
Medium
High
Critical
KEV: 0
EPSS: +0.0
CVSS: +39
POC: 0
Vendor Status
Ubuntu
Priority: Mediumpam
| Release | Status | Version |
|---|---|---|
| trusty | needs-triage | - |
| xenial | needs-triage | - |
| bionic | needs-triage | - |
| focal | needs-triage | - |
| upstream | needs-triage | - |
| jammy | released | 1.4.0-11ubuntu2.6 |
| noble | released | 1.5.3-5ubuntu5.4 |
| oracular | released | 1.5.3-7ubuntu2.3 |
| plucky | released | 1.5.3-7ubuntu4.3 |
| questing | released | 1.5.3-7ubuntu6 |
Debian
Bug #1107919pam
| Release | Status | Fixed Version | Urgency |
|---|---|---|---|
| bullseye | fixed | 1.4.0-9+deb11u2 | - |
| bullseye (security) | fixed | 1.4.0-9+deb11u2 | - |
| bookworm | fixed | 1.5.2-6+deb12u2 | - |
| forky, sid, trixie | fixed | 1.7.0-5 | - |
| experimental | fixed | 1.7.0-4 | - |
| (unstable) | fixed | 1.7.0-5 | - |
Share
External POC / Exploit Code
Leaving vuln.today
Destination URL
POC code from unknown sources may be malicious, contain backdoors, or be fake.
Always review and test exploit code in a safe, isolated environment (VM/sandbox).
Verify the source reputation and cross-reference with known databases (Exploit-DB, GitHub Security).