NGINX Plus, NGINX Open Source: contain code execution

At a glance

NGINX Plus, NGINX Open Source: remote code execution. This 2026-05-26 case examines 4 version entries and 1 CVEs, documented releases and checks suited to network access, using CERTFR-2026-AVI-0643.

AI illustration: a dark cybersecurity technology space with restrained golden lighting Illustration · fictional scene
In this article

Retrospective for 2026-05-26, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.

What this advisory changes in your environment

The starting point is CERTFR-2026-AVI-0643, published on 2026-05-26. Its scope includes NGINX Plus, NGINX Open Source. Reported consequences are denial of service, remote code execution. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.

This case contains 4 version entries; CVE identifier count: 1. Track remediation by component: a successful overall update does not demonstrate that NGINX Plus and NGINX Open Source each received their respective fix.

Products and versions to examine

Reference
CERTFR-2026-AVI-0643
Source first published
2026-05-26
Latest source revision available for this day
2026-05-26
Named components
NGINX Plus, NGINX Open Source
CVE identifiers
CVE-2026-9256
ComponentPublished condition
NGINX Plus37.x : < 37.0.1.1
NGINX Open Sourcepostérieures à 1.31.0 : < 1.31.1
NGINX Open Source1.x : < 1.30.2

For NGINX Plus, the published condition is “37.x : < 37.0.1.1”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of NGINX Plus, NGINX Open Source does not close this case.

Mechanism and prerequisites

Code execution can give an attacker the permissions of the affected process. Check the service account and reachable network destinations. Component isolation can reduce lateral movement opportunities, but does not replace the fix.

For CERTFR-2026-AVI-0643, the retained documents do not provide a suitably dated primary CVE record to establish this case’s prerequisites. Required authentication, user interaction and active exploitation therefore remain unestablished here; they are not inferred from NGINX Plus, NGINX Open Source or the risk category alone.

Choose the appropriate intervention

  1. Locate NGINX Plus instances, running releases and service owners. Record condition 37.x : < 37.0.1.1 in the ticket alongside reference CERTFR-2026-AVI-0643.
  2. Compare the installed branch with the vendor’s NGINX Plus release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
  3. After changing NGINX Plus, capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.

Verify the fix in a real workflow

Validation scenario to adapt for NGINX Plus, NGINX Open Source: For NGINX Plus, test an authorised business flow from each zone reaching the service and confirm management restrictions. If a redundant pair exists, verify both nodes and rule persistence after failover during a planned maintenance window. This is a proposed defensive check, not a claim that testing was performed against third-party systems.

Limit of case CERTFR-2026-AVI-0643: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.

Questions specific to this case

Which condition should be checked for NGINX Plus?

Advisory CERTFR-2026-AVI-0643 states: NGINX Plus — 37.x : < 37.0.1.1. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.

Why not use one fix for NGINX Plus and NGINX Open Source?

CERTFR-2026-AVI-0643 distinguishes these components within a scope containing 4 entries. Match each branch to its own update documentation and functional check.

What is still needed to assess NGINX Plus, NGINX Open Source exposure?

For NGINX Plus, NGINX Open Source, establish the running version, the path to the component and process permissions. The sources retained for CERTFR-2026-AVI-0643 do not establish every prerequisite or active exploitation.

Sources and related reading

Practical guide : Software inventory: prepare for end of support

Explore the decision addressed in this case

Complete source advisory inventory

The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.

Official source · CERTFR-2026-AVI-0643
Advisory revision : · Checked on :

Affected systems · 4

Original French wording is retained to avoid ambiguous translations of version conditions.

  1. NGINX Plus versions Rx antérieures à R36 P5 ou R32 P7
  2. NGINX Plus versions 37.x antérieures à 37.0.1.1
  3. NGINX Open Source versions postérieures à 1.31.0 antérieures à 1.31.1
  4. NGINX Open Source versions 1.x antérieures à 1.30.2

Historical note from this revision: check current patch availability with the vendor before acting.

L'éditeur indique que les versions 0.x de Nginx Open Source n'auront pas de correctifs

CVE identifiers · 1