# CVE-2026-61897: accountsservice: incomplete privilege drop when running Ubuntu-specific language helper scripts

> Local attackers can escalate privileges to root because Ubuntu's accountsservice fails to fully drop root privileges when launching language helper scripts.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 20 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-8h74-384h-cv6c, UBUNTU-CVE-2026-61897

## What is CVE-2026-61897?

CVE-2026-61897 is a high-severity vulnerability in Canonical accountsservice, published on 20 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Ubuntu-specific patch to AccountsService before 23.13.9-8ubuntu7 only partially drops privileges before launching language helper scripts. It changes the effective UID/GID to the target user but leaves the real UID as 0 (root). A shell spawned by a helper script inherits ruid=0 and may reset its effective UID to root, enabling local privilege escalation.

Weakness: CWE-273 (Improper Check for Dropped Privileges)

## Which versions are affected by CVE-2026-61897?


## How do I fix CVE-2026-61897?

Apply the vendor's patch.

## Is CVE-2026-61897 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61897 and fix it if it is affected.

What it is: CVE-2026-61897 is a high-severity vulnerability in Canonical accountsservice, published on 20 Aug 2026. 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-2026-61897 in the wild and no public exploit code.

Affected product: Canonical accountsservice. 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-2026-61897/ (Markdown: https://insights.sbomify.com/CVE-2026-61897/index.md)
```

## Sources

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

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