BuildKit supports interactive containers based on built images in addition to ordinary build steps. The intended control is the security.insecure entitlement, which must be enabled in buildkitd configuration and authorized by the build request. In the vulnerable path, the interactive container API did not validate entitlements under the same conditions as ordinary build requests, so an attacker-controlled frontend or LLB generator could request elevated security mode. The published technical details identify Client.NewContainer, Container.Start, and the StartRequest.SecurityMode field as relevant components. A custom frontend can be selected through a Dockerfile # syntax directive or the --frontend option of buildctl build. The advisory establishes creation of an elevated container; the CNA description does not establish a specific container escape sequence to the host, so host compromise should be treated as a possible consequence rather than an automatic result in every deployment.