Pardus LightDM Greeter EUVD-2026-75019

Exploitation requires: (1) a valid local user account on the target system - no remote access vector applies; (2) the affected system must be running Pardus Linux with the Pardus LightDM Greeter package installed and active as the display manager; (3) the vulnerable version must be prior to 0.4.15. No special system configuration, enabled feature flag, or additional software is required beyond the default Pardus desktop installation. Limiting factors: the attacker must have local interactive access or an active local shell session; remote exploitation is not possible based on the AV:L CVSS vector; scope is unchanged (S:U), meaning the flaw does not directly break out of the local system boundary; availability impact is none (A:N), so the greeter itself is not crashed or disrupted.

The CVSS 3.1 base score of 7.1 reflects a genuinely meaningful local privilege risk: low attack complexity (AC:L), no user interaction (UI:N), and only a low-privilege account required (PR:L), yielding high confidentiality and integrity impact. Real-world risk is constrained by the local attack vector - an attacker must already have a shell or interactive session on the target system, which limits opportunistic remote exploitation. EPSS data is not provided, and the vulnerability is not listed in the CISA KEV catalogue, indicating no confirmed active exploitation at time of analysis. No public proof-of-concept code has been identified. The combination of AV:L and the Pardus-specific deployment base (primarily Turkish government, public-sector, and education environments) further bounds the realistic threat population. For organizations running Pardus desktops or thin clients, however, this is a meaningful local escalation path on login-facing infrastructure. There is no CVSS conflict - the local vector is consistent with a file-permission misconfiguration in a greeter daemon. Missing: EPSS score, detailed affected-resource specification, and independently verified patch content.

An attacker who already holds a low-privileged local account on a Pardus desktop or thin-client system - for example, a student account in a school lab or a restricted operator account in a government workstation - locates a world-readable or world-writable greeter resource such as a configuration file or session credential store. By reading the resource, the attacker may extract authentication material or sensitive configuration; by writing to it, the attacker may alter login behavior or inject malicious configuration to influence subsequent authentication flows. No public proof-of-concept exists, but the low attack complexity (AC:L) suggests the technique is straightforward once the misconfigured resource is identified.