Description
Description


NGINX JavaScript (njs) has a vulnerability where the built-in njs engine leaks a libxml2 parser context when xml.parse() fails. The failure path did not register cleanup and the context was not released for the lifetime of the process. An unauthenticated attacker may send requests with malformed XML and can cause unbounded memory growth in long-lived NGINX worker processes.

Impact


This vulnerability may allow remote attackers to send requests that trigger repeated parsing of malformed XML and may lead to NGINX worker termination or denial of service. 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.
Published: 2026-10-14
Score: 6.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service
Action: Apply Workaround
AI Analysis

Impact

The vulnerability arises when the NGINX JavaScript (njs) library fails to clean up a libxml2 parser context after a malformed XML parsing error. The leaked context remains allocated for the lifetime of a worker process, causing unbounded memory growth. This can lead to worker termination or a denial of service for requests that repeatedly trigger the parse error. The weakness is an uncontrolled memory allocation flaw (CWE‑401).

Affected Systems

The affected product is the NGINX JavaScript (njs) module distributed as part of F5 NGINX. No specific version information is provided in the CVE data, and confirmed support status is not indicated. The vulnerability is present in all current releases that include the vulnerable parsing routine in the njs engine.

Risk and Exploitability

The CVSS score of 6.9 indicates moderate to high severity. The EPSS score of <1% indicates a low likelihood of exploitation, and the vulnerability is not listed in CISA’s KEV catalog, suggesting limited or no public exploitation yet. The likely attack vector is remote, where an unauthenticated attacker sends crafted XML payloads to the data plane; the flaw does not require privileged access or control plane interaction. Because the flaw manifests only when parsing fails, repeated detection of malformed XML can be used to exhaust memory and eventually cause service disruption.

Generated by OpenCVE AI on October 15, 2026 at 19:55 UTC.

Remediation

Vendor Workaround

Use the QuickJS engine with js_engine qjs;, which is not affected. Where migration is not possible, avoid passing attacker-controlled XML to xml.parse(), reject or rate-limit malformed input, and use worker memory limits.


OpenCVE Recommended Actions

  • Configure NGINX to use the QuickJS engine with js_engine qjs; this replaces njs and eliminates the vulnerable XML parser.
  • If migration to QuickJS is not viable, configure NGINX to reject or rate‑limit XML payloads that fail parsing, and avoid allowing attacker‑controlled XML to reach xml.parse().
  • Enforce worker memory limits to prevent unbounded memory consumption.
  • Deploy monitoring for excessive memory usage in NGINX workers and automatically restart the worker or the process when thresholds are exceeded.

Generated by OpenCVE AI on October 15, 2026 at 19:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 16 Oct 2026 22:45:00 +0000

Type Values Removed Values Added
First Time appeared F5
F5 nginx Javascript
Vendors & Products F5
F5 nginx Javascript

Thu, 15 Oct 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 14 Oct 2026 15:00:00 +0000

Type Values Removed Values Added
Description Description NGINX JavaScript (njs) has a vulnerability where the built-in njs engine leaks a libxml2 parser context when xml.parse() fails. The failure path did not register cleanup and the context was not released for the lifetime of the process. An unauthenticated attacker may send requests with malformed XML and can cause unbounded memory growth in long-lived NGINX worker processes. Impact This vulnerability may allow remote attackers to send requests that trigger repeated parsing of malformed XML and may lead to NGINX worker termination or denial of service. 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.
Title NGINX ngx_http_js_module vulnerability
Weaknesses CWE-401
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'}


Subscriptions

F5 Nginx Javascript
cve-icon MITRE

Status: PUBLISHED

Assigner: f5

Published:

Updated: 2026-10-15T16:43:46.495Z

Reserved: 2026-09-30T21:56:14.628Z

Link: CVE-2026-101025

cve-icon Vulnrichment

Updated: 2026-10-15T16:38:39.431Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-14T15:17:01.880

Modified: 2026-10-15T17:17:08.247

Link: CVE-2026-101025

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-16T22:30:13Z

Weaknesses
  • CWE-401

    Missing Release of Memory after Effective Lifetime