When using the njs engine, the out-of-bounds write corrupts adjacent heap objects, leading to an immediate crash of the NGINX worker process. When using the QuickJS engine, the vulnerability causes memory leakage on every request, resulting in memory exhaustion. The nginx-saml reference implementation is specifically vulnerable during SAML signature verification, as it processes the InclusiveNamespaces/@PrefixList from untrusted SAML messages before verifying the digital signature. Consequently, attackers can trigger the crash or memory growth using crafted SAML Response, Assertion, LogoutRequest, or LogoutResponse packets. While remote code execution has not been observed, it remains a theoretical possibility depending on specific platform memory layout.

Impact

The vulnerability impacts the availability of NGINX instances processing XML or SAML data. Successful exploitation leads to denial of service through repeatable worker process restarts (njs engine) or rapid worker memory growth (QuickJS engine). Because the flaw triggers before SAML signature validation, attackers do not require valid credentials or legitimate SAML tokens to impact the target service.

Recommendation

• Identify all instances using the nginx-saml reference implementation and upgrade to the patched version once available.
• Review NGINX configurations for usages of xml.exclusiveC14n() that process untrusted XML input and implement rigorous input validation for the PrefixList attribute.
• Monitor NGINX error logs for recurring "worker process exited with signal" events, which may indicate crash-based denial of service attempts.
• Monitor memory usage of NGINX worker processes to detect memory exhaustion patterns indicative of QuickJS exploitation.