AIKIDO-2026-10538

TL;DR

In src/lib/helpers/parse.js, after decrypt() runs, string values that still match the encrypted: ciphertext form were passed through the same evalKeyValue / eval path and the expand / resolveEscapeSequences path as normal secrets. A value can therefore embed shell command substitution (for example $(…) in the payload) that is executed while resolving the variable, even though the value is only intended to be opaque encrypted material. Before the change, the parser had no isEncrypted / encrypted: check before those steps. The update treats encrypted-prefixed values as non-evaluatable: it sets encryptedPrefixed from isEncrypted(this.parsed[key]) and skips both the eval and escape-expansion blocks when that flag is true, so encrypted: secrets are not expanded or run as shell commands.