Kanywst

The `trusted-repos-policy` performs case-sensitive comparisons of an image's `registry` hostname against reject and allow lists, despite DNS names being case-insensitive. This allows a bypass of reject-list configurations by using uppercase or mixed-case hostnames, leading the admission policy to accept resources that the container runtime then pulls from a prohibited image registry. Allow-list configurations are not bypassed but instead fail closed by denying hostnames with different casing.

An issue exists where the server can be coerced into making requests to internal resources during organization domain HTTP verification. This occurs because the challenge fetch process utilizes the default `http.Get` function in Go instead of a protected client. Attackers can register domains that redirect to loopback, internal, or cloud metadata addresses, enabling them to scan ports and map internal networks. This is a server-side request forgery (SSRF), which is a flaw that allows an attacker to induce the server-side application to make requests to an unintended location.

In Kong Mesh running in universal mode with a MeshIdentity whose SPIFFE ID path template derives from the dataplane's `kuma.io/workload` label, the XDS authenticator in kuma-cp only validates that label when the dataplane token is bound to a workload. Since workload binding is optional, a dataplane using a tags-bound token can register with the `kuma.io/workload` label set to any value, allowing it to obtain the SPIFFE identity of another workload.