Zer0D4Y5

A licensed deployment with a configured SAML client can authenticate an identity from an assertion that fails the audience check. If the identity provider uses assertion-level signing, an attacker can combine a valid IdP-signed assertion for a victim (intended for any audience) with their own valid assertion for the target audience. This occurs because the `validateSamlResponseAudience` function accepts an audience from one assertion while the `extractAllClaims` function retrieves the final NameID and attributes from another. Additionally, an assertion issued to a different SuperTokens deployment using the shared default `saml sp entity id` can satisfy the audience check of the target deployment. Successful exploitation allows an attacker to authenticate as the victim IdP user.

A path traversal weakness exists where the software fails to validate path segments in the resource argument of the `resource.get()` and `resource.post()` functions. This allows namespaced Common Expression Language (CEL) policies—a declarative language used for policy enforcement—to escape their designated namespace. An attacker with permissions to create a NamespacedValidatingPolicy can use `..` segments to read and write arbitrary cluster objects via the admission controller's ServiceAccount, potentially resulting in a full cluster takeover.

An ACL bypass occurs when explicit deny rules based on forbidden identity metadata templates within wildcard grants are silently dropped. This allows attackers with identity metadata containing wildcard or path segments to access paths that should be restricted within the broader wildcard-granted scope.

An issue exists in the `OctKey.import key()` function within `authlib/jose/rfc7518/oct key.py` where asymmetric-key markers are only checked at byte zero. Because PEM loaders accept leading whitespace, comments, or a byte-order mark, the `POSSIBLE UNSAFE KEYS` check fails to identify prefixed asymmetric key material. In deployments using a mixed algorithm registry configured with PEM or certificate bytes containing such prefixes, an unauthenticated attacker with knowledge of those public-key bytes can use them as an HMAC secret to forge HS256 tokens with arbitrary identity or authorization claims.

A cross-namespace authorization bypass exists in the ACL binding rules component. This issue may allow an attacker to obtain elevated Consul privileges.

A mismatch occurs because the middleware evaluates the raw request target to determine if path-scoped middleware should run, whereas the Fastify router resolves an absolute-form request target to its path before dispatching. This discrepancy allows a request using an absolute-form target to reach the route handler while skipping path-scoped middleware used for authentication, authorization, rate limiting, or auditing. An unauthenticated network attacker can exploit this behavior to bypass path-based access controls.