Contact us
← Article questionsWhat should we do?

CVEHit Business Advisory by IntegrityLab.ai

What should we do?

NGINX HTTP/2 flaws can crash or take over web servers — CVE-2026-123007 and CVE-2026-123633: Business Triage

UPDATE: If records show a break-in, start incident response now. A government security center reports exploitation of an unspecified NGINX flaw that no other source has confirmed. Apply the fix for your affected NGINX build now. Check separately for the other three flaws even if HTTP/2 is off.

Do Now

  • System owner: update NGINX Open Source to 1.31.9 or 1.30.7, or NGINX Plus to 37.3.0.1 or 37.0.8.1, then restart NGINX.
    Proof the update is done
    • Completion evidence for each server:
      • Version or package installed after the update.
      • Source of that record.
      • Date checked.
    • A configuration reload alone does not replace the running program. Confirm the running version after a restart.
    • For a distribution package claiming a fix below 1.30.7, the distribution's notice naming both CVEs.
  • Operations owner: where an immediate update is not possible, turn off HTTP/2 on affected listeners until the update is done.
    What to know
    • F5 lists no workaround. F5 describes both flaws as affecting configurations that use HTTP/2, so with HTTP/2 off the stated condition is not met. This is a stopgap, not the fix.
    • Services that need HTTP/2, such as gRPC, cannot use this stopgap.
    • On the retired community ingress-nginx controller, HTTP/2 is on by default (use-http2). No fixed release will come. Plan a move to a maintained controller.
  • Provider: ask each vendor whose product or hosting includes NGINX whether it is affected and when a fix ships.
    What to ask
    • Ask for:
      • Which NGINX version the product or service runs.
      • Whether HTTP/2 is on.
      • The fix date.
    • Keep the reply as evidence.

Do Next

  • Security owner: recheck CISA, F5 and WASOC for changes to the exploitation status.
    What to recheck
    • CISA's assessment in each CVE record, dated November 18, 2026.
    • The CISA Known Exploited Vulnerabilities (KEV) catalog. None of the five flaws appeared in catalog 2026.11.18 when we checked on November 20, 2026.
    • WASOC advisory 20261119001, which names no exploited CVE yet.
    • nginx.org security advisories and F5 articles K000163926 and K000163928.
    • Date of each recheck.

← Back to article questions

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…