CVE-2026-8711: CWE-122 Heap-based Buffer Overflow in F5 NGINX JavaScript
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.
AI Analysis
Technical Summary
The vulnerability in NGINX JavaScript (version 0.9.4) involves a heap-based buffer overflow triggered by the js_fetch_proxy directive when it uses client-controlled variables such as $http_*, $arg_*, or $cookie_*. When a location invokes ngx.fetch(), an attacker can send specially crafted HTTP requests to exploit this flaw. This leads to a heap buffer overflow in the NGINX worker process, causing a crash and restart. Furthermore, if Address Space Layout Randomization (ASLR) is disabled or bypassed, the attacker may achieve remote code execution. The vulnerability is tracked as CWE-122 and has a CVSS 3.1 base score of 8.1, indicating high severity. The vendor has not provided a patch or official remediation at this time.
Potential Impact
Successful exploitation can cause the NGINX worker process to crash and restart due to a heap buffer overflow. On systems without ASLR or where ASLR can be bypassed, attackers may execute arbitrary code remotely. This impacts confidentiality, integrity, and availability of the affected system. No known exploits in the wild have been reported so far.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid configuring js_fetch_proxy with client-controlled variables or disable the affected functionality if possible. Monitor vendor communications for updates on patches or mitigations.
CVE-2026-8711: CWE-122 Heap-based Buffer Overflow in F5 NGINX JavaScript
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 v3.1
Score 8.1high
Affected software
pkg:github/nginx/nginx-javascriptRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in NGINX JavaScript (version 0.9.4) involves a heap-based buffer overflow triggered by the js_fetch_proxy directive when it uses client-controlled variables such as $http_*, $arg_*, or $cookie_*. When a location invokes ngx.fetch(), an attacker can send specially crafted HTTP requests to exploit this flaw. This leads to a heap buffer overflow in the NGINX worker process, causing a crash and restart. Furthermore, if Address Space Layout Randomization (ASLR) is disabled or bypassed, the attacker may achieve remote code execution. The vulnerability is tracked as CWE-122 and has a CVSS 3.1 base score of 8.1, indicating high severity. The vendor has not provided a patch or official remediation at this time.
Potential Impact
Successful exploitation can cause the NGINX worker process to crash and restart due to a heap buffer overflow. On systems without ASLR or where ASLR can be bypassed, attackers may execute arbitrary code remotely. This impacts confidentiality, integrity, and availability of the affected system. No known exploits in the wild have been reported so far.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid configuring js_fetch_proxy with client-controlled variables or disable the affected functionality if possible. Monitor vendor communications for updates on patches or mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- f5
- Date Reserved
- 2026-05-15T20:10:29.764Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a0c757aec166c07b0b402b4
Added to database: 05/19/2026, 14:36:42 UTC
Last enriched: 05/26/2026, 20:32:54 UTC
Last updated: 07/31/2026, 19:23:00 UTC
Views: 165
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.