CVE REMEDIATION GUIDE
Priority reviewHighFixed-version data available

CVE-2026-27654 remediation guide

F5 NGINX Open Source, NGINX Plus, Red Hat Enterprise Linux 10

NGINX Open Source and NGINX Plus have a vulnerability in the ngx_http_dav_module module that might allow an attacker to trigger a buffer overflow to the NGINX worker process; this vulnerability may result in termination of the NGINX worker process or modification of source or destination file names outside the document root. This issue affects NGINX Open Source and NGINX Plus when the configuration file uses DAV module MOVE or COPY methods, prefix location (nonregular expression location configuration), and alias directives. The integrity impact is constrained because the NGINX worker proce...

Open CVE record
ProductF5 NGINX Open Source, NGINX Plus, Red Hat Enterprise Linux 10
Affected versions>= 1.29.0 < 1.29.7, >= 0.5.13 < 1.28.3, >= R36 < R36 P3, >= R35 < R35 P2, >= R34, >= R33, >= R32 < R32 P5, r32, r33, r34, r35, r36, >= 0.5.13 <= 0.9.7, >= 1.0.0 < 1.28.3
Fixed versions1.28.3, 1.29.7
Priority basisPriority · CVSS 8.8 · EPSS 21.7%
01

Identify the affected asset

Confirm whether F5 NGINX Open Source, NGINX Plus, Red Hat Enterprise Linux 10 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 1.29.0 < 1.29.7, >= 0.5.13 < 1.28.3, >= R36 < R36 P3, >= R35 < R35 P2, >= R34, >= R33, >= R32 < R32 P5, r32, r33, r34, r35, r36, >= 0.5.13 <= 0.9.7, >= 1.0.0 < 1.28.3. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

FIRST EPSS indicates an elevated probability of exploitation. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 1.28.3, 1.29.7. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.