Description
Isar is an integration system for automated root filesystem generation. In versions 0.11 and newer, /etc/apt/trusted.gpg.d is created manually during bootstrap setup to be able to deploy local keys. By that, the directory is owned by the calling user (the one that executes Isar) instead of root. If the calling user's id is identical to one of an unprivileged user inside the image, this user is able to alter existing keys and deploy new ones, silently breaking the apt repo integrity protection. The issue is has no impact on those images that use an immutable rootfs, or if apt is never invoked. Changing only the keys does not trigger an exploit, it's just one step in a chain. An attacker would also have to manipulate a remote repo or intercept non-secure communication with it. This issue has been patched via commit 29e84ed.
Published: 2026-10-23
Score: 5.1 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Integrity compromise of package repository via key tampering
Action: Patch
AI Analysis

Impact

Isar, an automated root filesystem generator, creates the directory /etc/apt/trusted.gpg.d during bootstrap so local GPG keys can be deployed. In all versions 0.11 and newer the directory is owned by the user who runs Isar rather than by root. If that user’s UID matches an unprivileged user inside the resulting image, the user can modify or add keys to the trusted list. Changing these keys silently breaks the apt repository’s integrity protection, enabling a later attacker to deliver malicious packages or manipulate package delivery. The vulnerability itself does not provide a direct exploitation path; it is a prerequisite for further attacks that require either a malicious remote repository or interception of non‑secure communications.

Affected Systems

The affected product is Isar from ilbers, version 0.11 and beyond. The vulnerability exists in configurations where Isar is executed with a user whose UID is reused by an unprivileged image user, and where apt is active in the image.

Risk and Exploitability

The CVSS score of 5.1 indicates a moderate severity. An EPSS value is unavailable, and the issue is not listed in CISA’s KEV catalog. The likely exploitation path requires local execution of Isar by the attacker or ensuring the attacker’s UID matches a non‑privileged image user, followed by manipulation of a remote repository or insecure transport to deliver compromised packages. The attack vector is thus local with a chain of subsequent steps that are not guaranteed to succeed without additional conditions.

Generated by OpenCVE AI on October 23, 2026 at 16:39 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the upstream patch (commit 29e84ed301c8d25c570300cf82b563b7961392b0) that sets /etc/apt/trusted.gpg.d ownership to root.
  • Run Isar bootstrap under a dedicated root or system user rather than a shared UID that could match an image user.
  • Verify that no untrusted keys have been added to /etc/apt/trusted.gpg.d and that only trusted keys are present before allowing apt package installation.

Generated by OpenCVE AI on October 23, 2026 at 16:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 23 Oct 2026 23:15:00 +0000

Type Values Removed Values Added
First Time appeared Ilbers
Ilbers isar
Vendors & Products Ilbers
Ilbers isar

Fri, 23 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 23 Oct 2026 14:45:00 +0000

Type Values Removed Values Added
Description Isar is an integration system for automated root filesystem generation. In versions 0.11 and newer, /etc/apt/trusted.gpg.d is created manually during bootstrap setup to be able to deploy local keys. By that, the directory is owned by the calling user (the one that executes Isar) instead of root. If the calling user's id is identical to one of an unprivileged user inside the image, this user is able to alter existing keys and deploy new ones, silently breaking the apt repo integrity protection. The issue is has no impact on those images that use an immutable rootfs, or if apt is never invoked. Changing only the keys does not trigger an exploit, it's just one step in a chain. An attacker would also have to manipulate a remote repo or intercept non-secure communication with it. This issue has been patched via commit 29e84ed.
Title Isar: Unprivileged user ownership of trusted repository GPG public keys storage after bootstrap
Weaknesses CWE-1290
References
Metrics cvssV3_1

{'score': 5.1, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-23T20:57:39.282Z

Reserved: 2026-06-16T16:16:32.628Z

Link: CVE-2026-55222

cve-icon Vulnrichment

Updated: 2026-10-23T20:43:47.852Z

cve-icon NVD

Status : Deferred

Published: 2026-10-23T15:17:32.563

Modified: 2026-10-23T21:17:24.003

Link: CVE-2026-55222

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-23T23:00:13Z

Weaknesses
  • CWE-1290

    Incorrect Decoding of Security Identifiers