Skip to content
Web

CVE-2026-18329

8.8
High
EPSS 0.38%Patch availableSep 3, 2026

NGINX njs/QuickJS bug can fail-open js_access, allowing auth bypass via crafted HTTP requests

common questions

Is CVE-2026-18329 being exploited?

Not confirmed. CVE-2026-18329 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.

How severe is CVE-2026-18329?

CVE-2026-18329 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-18329?

Yes. A fix has been recorded for CVE-2026-18329. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-18329 affect?

CVE-2026-18329 affects NGINX JavaScript (njs), QuickJS (qjs), NGINX instances using js_access handlers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-18329?

Apply vendor patch/update njs/qjs; disable or restrict js_access until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
NGINX JavaScript (njs)QuickJS (qjs)NGINX instances using js_access handlers
impact

Unauthenticated attackers can bypass js_access auth/authorization checks via crafted HTTP requests that trigger async js_access errors.

action required

Immediate action required

affected versions
F5 NGINX JavaScript
  • affected>= 1.0.0 and < 1.0.1
  • affected>= 0.9.9 and < *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free