# CVE-2026-52727: lxc-ci: Pacman keyring stored in archlinux image with a private key

> Attackers can execute arbitrary code as root by signing malicious packages with a hardcoded private key found in LXC Arch Linux images.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-52727, GHSA-4h59-f67g-5qxp, UBUNTU-CVE-2026-52727

## What is CVE-2026-52727?

CVE-2026-52727 is a high-severity vulnerability in lxc-ci, published on 17 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

lxc-ci contains continuous integration and image-build scripts for LXC. Prior to the 2026-05-28 Arch Linux image publication, images built from images/archlinux.yaml retain the same pacman local-signing private key in /etc/pacman.d/gnupg and redistribute it to every container or virtual machine created from that image. An attacker who controls an HTTP package mirror or can intercept mirror traffic can use the shared pacman signing private key to sign modified packages that affected clients accept as trusted. Installing those packages permits arbitrary code execution as root on the client system. This issue is fixed in Arch Linux images published on or after 2026-05-28.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

Upgrade to a fixed version.

## Is CVE-2026-52727 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52727 is a high-severity vulnerability in lxc-ci, published on 17 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-52727 in the wild and no public exploit code.

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

## Sources

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

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