lxc-ci: Pacman keyring stored in archlinux image with a private key
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| lxc | lxc-ci | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Lxc | Lxc-ci |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.594% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Lxc
Lxc lxc-ci |
|
| Vendors & Products |
Lxc
Lxc lxc-ci |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | lxc-ci: Pacman keyring stored in archlinux image with a private key | |
| Weaknesses | CWE-321 | |
| References |
| |
| Metrics |
cvssV3_1
|