Siemens kas EUVD-2026-58723

Exploitation requires all five of the following conditions to be met simultaneously: (1) The attacker must have already obtained write access to a Git repository that the victim's kas configuration references as an include source - this is a hard prerequisite requiring prior supply-chain compromise. (2) The victim's kas configuration file must include a configuration file sourced from that attacker-controlled repository. (3) The repository reference in the victim's kas file must use a tag rather than a full commit hash (kas warns about this but does not prevent it). (4) The cryptographic key used to validate the tag or commit signature must be stored as a file within a repository (not specified out-of-band or via fingerprint). (5) No key fingerprint must be configured, and the victim must not set the '_source_dir' key. Exploitation is limited by the requirement for prior upstream repository compromise, the non-default key-storage pattern, the absence of a pinned fingerprint, and tag-based (rather than commit-hash-based) pinning - each condition independently reduces the attack surface.

No CVSS vector or EPSS score is provided for this CVE, so severity cannot be formally graded; all risk signals must be inferred from the description and advisory data. The attack requires a highly specific convergence of five independent conditions: the attacker must have already compromised a referenced upstream repository, that repository must be pinned by tag rather than commit hash, the signature key must be stored as a file within a repository (not out-of-band), no fingerprint must be configured, and the victim must not set _source_dir. Each of these is a non-default or operationally discouraged configuration (kas itself issues a warning when tags are used without commit IDs). This places the realistic exploitability significantly below what a high-CVSS supply-chain attack might suggest. That said, the impact is severe in affected pipelines: a successful exploit bypasses the entire cryptographic trust model, allowing silent injection of arbitrary build configuration. There is no KEV listing and no known public exploit, making this a theoretical but credible supply-chain risk for Yocto/embedded Linux CI environments.

An attacker who has compromised an upstream Git repository referenced in a victim's kas build configuration modifies that repository's included kas configuration file to redirect the signature validation key path to an attacker-controlled key. Because kas checks out and parses this configuration before validating the tag signature, the substituted key is loaded, allowing the attacker's tag signatures to pass validation - effectively granting silent control over the build inputs. No public proof-of-concept code has been identified at time of analysis, but the attack is logically constructable from the advisory description alone.