Description
NGINX JavaScript (njs) has a vulnerability in the XML module's namespace prefix list parser, reachable through the xml.exclusiveC14n() method. An unauthenticated remote attacker can trigger it when an affected NGINX configuration passes an externally controlled XML namespace prefix list to that method. Both the njs and the QuickJS (qjs) engines are affected. A crafted prefix list causes an out-of-bounds write past the end of a heap allocation. With the njs engine, which is the engine used when the js_engine directive is absent, this corrupts adjacent objects and crashes the NGINX worker. With the QuickJS engine, the same call additionally leaks the prefix list on every invocation, causing worker memory to grow across requests. The official nginxinc/nginx-saml reference implementation is affected during SAML signature verification. It reads InclusiveNamespaces/@PrefixList from an untrusted SAML message and passes it to xml.exclusiveC14n() before the signature has been verified, so a valid SAML signature is not required. A crafted SAML Response, Assertion, LogoutRequest, or LogoutResponse is sufficient. Code execution has not been demonstrated and cannot be ruled out for all platforms, as the effect of the out-of-bounds write depends on conditions beyond the attacker's control.
Impact
This vulnerability allows remote attackers to cause a denial of service on the NGINX system, either through repeatable worker restarts or through worker memory growth or possibly trigger code execution. There is no control plane exposure; this is a data plane issue only.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker may crash NGINX workers or increase worker memory consumption when untrusted XML namespace data reaches a vulnerable NGINX JavaScript canonicalization method. The cited SAML reference implementation exposes this path before signature verification, so attackers do not need a valid SAML signature. Code execution remains unproven.
Executive priority
Treat this as an urgent availability risk for internet-facing NGINX deployments using affected XML or SAML processing. Immediately identify exposed configurations and apply F5 guidance when confirmed. Prioritize authentication infrastructure because repeated worker failure or memory growth could disrupt access. Escalate further if operational telemetry shows matching instability, while recognizing that the supplied evidence does not confirm active attacks.
Technical view
A crafted namespace prefix list passed to xml.exclusiveC14n() causes a heap out-of-bounds write in the njs XML parser. The njs engine can corrupt adjacent objects and crash workers; QuickJS additionally leaks memory per invocation. This is a data-plane vulnerability affecting both engines, with exploitability dependent on configuration and attacker-controlled input flow.
Likely exposure
Exposure requires an affected NGINX JavaScript deployment whose configuration passes externally controlled XML namespace prefix lists to xml.exclusiveC14n(). The official nginxinc/nginx-saml reference implementation is specifically identified as affected. The bundle lists NGINX JavaScript 0.7.10, but does not establish a complete affected-version range or fixed release.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no cited evidence of active exploitation. Exploitation does not require authentication or a valid SAML signature in the affected reference implementation. Demonstrated impacts are repeatable worker crashes and, with QuickJS, accumulating memory usage. Code execution has neither been demonstrated nor ruled out across all platforms.
Researcher notes
The prerequisite is important: vulnerable code alone is insufficient unless attacker-controlled prefix-list data reaches xml.exclusiveC14n(). Both supported engines are affected but exhibit different observed consequences. The out-of-bounds write makes impact platform-dependent; claims of remote code execution would exceed current evidence. The supplied version information is incomplete, so broader version assertions should await the vendor advisory.
Mitigation direction
Consult the F5 advisory for authoritative fixed releases or configuration guidance; the supplied sources name no patched version.
Identify and prioritize deployments using xml.exclusiveC14n() with externally influenced namespace prefix lists.
If operationally acceptable, disable affected SAML processing paths until vendor-directed remediation is applied.
Restrict untrusted access to exposed affected paths while preserving required authentication services.
Validation and detection
Inventory deployed NGINX JavaScript versions and determine whether njs or QuickJS is configured.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.