Critical severity · published May 19, 2026
CVE-2026-8711
NGINX JavaScript vulnerability
9.8
CVSS
9.7%
EPSS
No
On KEV
Description
NGINX JavaScript has a vulnerability when the js_fetch_proxy directive is configured with at least one client-controlled NGINX variable (for example, $http_*, $arg_*, $cookie_*) and a location invoking the ngx.fetch() operation from NGINX JavaScript. An unauthenticated attacker can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow in the NGINX worker process leading to a restart. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)9.7% · higher than 95% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
NJ
NGINX JavaScript · F5
0.9.4 before 0.9.9 · source: vendor
NJ
Njs · F5
0.9.4 before 0.9.9 · source: NVD
Affected product
NJ
NGINX JavaScript
F5
More from NGINX JavaScript
8.2
CVE-2026-18329
NGINX ngx_http_js_module vulnerability
8.1
CVE-2026-78689
NGINX ngx_http_js_module vulnerablility
7.5
CVE-2026-78222
NGINX ngx_http_js_module vulnerability
6.5
CVE-2026-101019
NGINX ngx_http_js_module vulnerability
5.3
CVE-2026-101025
NGINX ngx_http_js_module vulnerability