CVE REMEDIATION GUIDE
Review reviewCriticalFixed-version data available

CVE-2026-6722 remediation guide

PHP Group PHP, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8

In PHP versions 8.2.* before 8.2.31, 8.3.* before 8.3.31, 8.4.* before 8.4.21, and 8.5.* before 8.5.6, the SOAP extension's object deduplication mechanism stores pointers to PHP objects in a global map without incrementing their reference counts. When an apache:Map node contains duplicate keys, processing the second entry overwrites the first in the temporary result map, freeing the original PHP object while its stale pointer remains in the map. A subsequent href reference to the freed node can copy the dangling pointer into the result. As PHP string allocations can reclaim the freed memory...

Open CVE record
ProductPHP Group PHP, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8
Affected versions>= 8.2.* < 8.2.31, >= 8.3.* < 8.3.31, >= 8.4.* < 8.4.21, >= 8.5.* < 8.5.6, >= 8.2.0 < 8.2.31, >= 8.3.0 < 8.3.31, >= 8.4.0 < 8.4.21, >= 8.5.0 < 8.5.6
Fixed versions8.2.31, 8.3.31, 8.4.21, 8.5.6
Priority basisReview · CVSS 9.5 · EPSS 0.74%
01

Identify the affected asset

Confirm whether PHP Group PHP, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8 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: >= 8.2.* < 8.2.31, >= 8.3.* < 8.3.31, >= 8.4.* < 8.4.21, >= 8.5.* < 8.5.6, >= 8.2.0 < 8.2.31, >= 8.3.0 < 8.3.31, >= 8.4.0 < 8.4.21, >= 8.5.0 < 8.5.6. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. 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: 8.2.31, 8.3.31, 8.4.21, 8.5.6. 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.