Isar EUVD-2026-109069

All of the following must hold: (1) the image was built with Isar >= 0.11, leaving /etc/apt/trusted.gpg.d owned by the calling (build) user; (2) that build user's uid is identical to an unprivileged user account that exists inside the generated image; (3) the attacker controls that in-image unprivileged account, giving write access to the keystore; and (4) per the advisory, altering keys alone is insufficient - the attacker must also manipulate a remote repository or intercept non-secure (unencrypted/unauthenticated) apt communication. Limiting factors: there is explicitly NO impact on images using an immutable rootfs or where apt is never invoked; exploitation is local only and requires the coincidental uid match (a non-default condition), so default builds without the uid collision are not affected.

This is a medium-severity integrity weakness (CVSS 5.1) whose real-world urgency is low-to-moderate, and the signals are broadly consistent rather than conflicting. The CVSS vector is AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N: local attack vector, high attack complexity, integrity-only impact. The vuln.today decision label is 'this_month' (not act_now/emergency), there is no CISA KEV listing, no EPSS probability was supplied, and no public exploit code was identified - all pointing to a non-urgent, difficult-to-exploit flaw rather than a mass-exploitation threat. One discrepancy should be verified with the vendor: the input vector states PR:N (unauthenticated), yet the GHSA advisory and description make clear the attacker must already be a local unprivileged user account inside the generated image whose uid happens to equal the build (Isar-executing) user's uid - that is a pre-existing local foothold, which argues for PR:L. The AC:H rating is well supported: exploitation depends on a non-default uid collision AND, by the advisory's own words, modifying the keys alone 'does not trigger an exploit' - the attacker must additionally manipulate a remote repository or intercept non-secure apt communication. Net: a genuine defense-in-depth regression (apt signature trust can be silently undermined) but gated behind multiple preconditions, so it is a patch-this-month item, not an emergency.

In an Isar-built image (>= 0.11) where the build was run under a uid that also exists as an unprivileged account inside the image, that in-image user overwrites the attacker-writable /etc/apt/trusted.gpg.d keys with their own GPG key. Combined with a man-in-the-middle position or control of a repository mirror, the attacker then serves forged packages that apt accepts as validly signed, undermining repository integrity. No public exploit code was identified at time of analysis; only the advisory and fix commit are referenced.