CVE
Debian LightDM local root escalation via writable shared directory
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 1.33.1-5
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.33.1-5.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Due to a Debian-specific patch in the lightdm package, a directory shared between LightDM and logged-in users was writable by the lightdm user running the unprivileged greeter. An attacker with local access and low-privilege login can use that write access to make the root-level LightDM process change ownership and permissions on other root-owned directories, escalating from the lightdm user to root.
Written by a model from the sources below. Verify against them.
Original description
Due to a Debian-specific patch, the directory used to share data between the LightDM and the users logging in was writable by the lightdm user of the unprivileged greeter process. A process running under the lightdm identity could leverage write access to that directory to force the LightDM process (running as root) to change ownership and permissions on other root-owned directories and escalate privileges from the lightdm user to root.
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Shipped in major Linux distributions
- Severity8.8/10CVSS 7.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 41 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.33.1-5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129246 (Due to a Debian-specific patch, the directory used to share data between the LightDM and the users logging in was writable by the lightdm…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129246 (entry last updated 2026-11-17):
Affected:
- Debian lightdm: from 1.10.3-2, fixed in 1.33.1-5; from 1.10.3-2, fixed in 1.32.0-6+deb13u1
Fixed versions: 1.33.1-5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129246 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129246 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://salsa.debian.org/xfce-extras-team/lightdm/-/commit/2721ed5e0e4d64a0dac99f74868857a989c1664c
- https://lists.debian.org/debian-security-announce/2026/msg00553.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129246
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129246"}.Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
- First seen by cve.now
Affected versions
- Debian lightdm
From 1.10.3-2 · fixed in 1.33.1-5; From 1.10.3-2 · fixed in 1.32.0-6+deb13u1
Evidence 4
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Link
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129246
Is CVE-2026-129246 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-129246?
lightdm: from 1.10.3-2 before 1.33.1-5; from 1.10.3-2 before 1.32.0-6+deb13u1.Source: cve.now feed data
How do I fix CVE-2026-129246?
Upgrade to a fixed version: 1.33.1-5.Source: cve.now feed data