Description
A vulnerability exists in NGINX JavaScript where a malformed HTTP response received by ngx.fetch() can crash an NGINX worker when trusted JavaScript reads Response.statusText. Exploitation requires control or influence over the fetched HTTP response.

Impact:
This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system. 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-09-02
Score: 8.7 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A malformed HTTP response received by the NGINX JavaScript (ngx_http_js_module) can cause the NGINX worker to crash when trusted JavaScript code accesses Response.statusText. The flaw does not provide code execution or data exfiltration; it merely results in a denial‑of‑service condition for the affected worker. The vulnerability requires the attacker to control or influence the fetched HTTP response, so it is a remote data‑plane issue only.

Affected Systems

The flaw targets deployments of F5’s NGINX JavaScript module that use the ngx.fetch API and reference Response.statusText in trusted scripts. No specific product version information is supplied, so any configuration where the module is enabled and fetch responses are processed in user scripts could be impacted.

Risk and Exploitability

The CVSS score of 8.7 marks this as a high‑severity issue. Although the vulnerability is not listed in the CISA KEV catalog, the potential for DoS makes it a priority for mitigations. The likely attack vector is remote: an attacker who can provide a crafted HTTP response to a trusted fetch endpoint can trigger the crash by causing a malformed statusText value.

Generated by OpenCVE AI on September 3, 2026 at 11:03 UTC.

Remediation

Vendor Workaround

Restrict ngx.fetch() destinations to trusted servers and avoid reading Response.statusText for responses from attacker-controlled or attacker-influenced endpoints. Using HTTPS with certificate verification reduces exposure to network-based response manipulation but does not protect against a malicious or compromised fetched server


OpenCVE Recommended Actions

  • Restrict ngx.fetch destinations to trusted servers only
  • Ensure that trusted JavaScript does not read or rely on Response.statusText for attacker‑controlled responses
  • Use HTTPS with certificate verification to limit network‑based response manipulation

Generated by OpenCVE AI on September 3, 2026 at 11:03 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 03 Sep 2026 11:00:00 +0000

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

Wed, 02 Sep 2026 10:45:00 +0000

Type Values Removed Values Added
Description A vulnerability exists in NGINX JavaScript where a malformed HTTP response received by ngx.fetch() can crash an NGINX worker when trusted JavaScript reads Response.statusText. Exploitation requires control or influence over the fetched HTTP response. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system. 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-476
References
Metrics cvssV3_1

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

cvssV4_0

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


Subscriptions

F5 Nginx Javascript
cve-icon MITRE

Status: PUBLISHED

Assigner: f5

Published:

Updated: 2026-09-02T17:59:40.463Z

Reserved: 2026-08-25T23:21:14.556Z

Link: CVE-2026-78222

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-02T16:17:23.557

Modified: 2026-09-02T19:23:13.660

Link: CVE-2026-78222

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-03T11:15:03Z

Weaknesses