Use-After-Free in SOAP using Apache map

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.5 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:M/U:Red · score source

EPSS

• CVE-2026-6722: 0.89% estimated exploitation activity in the next 30 days; percentile 59.80 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 region, an attacker with control over the SOAP request body can exploit this use-after-free to achieve remote code execution.

Published by the source

12 May 2026, 08:50 UTC

Last modified by the source

11 Nov 2026, 02:56 UTC

Source last checked

11 Nov 2026, 07:45 UTC

1. Revision 3 · amended · 11 Nov 2026

   Amended from osv record BIT-php-min-2026-6722

2. Revision 2 · amended · 11 Nov 2026

   Amended from osv record BIT-php-2026-6722

3. Revision 1 · created · 11 Nov 2026

   Published from osv record BIT-libphp-2026-6722

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-6722

Advisory: Use-After-Free in SOAP using Apache map
IDs: CVE-2026-6722, GHSA-85c2-q967-79q5
Record: https://patchnext.com/advisories/cve-2026-6722 (revision 3, source checked 11 Nov 2026, 07:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: php 8.5.6, 8.4.21, 8.3.31, 8.2.31; libphp 8.5.6, 8.4.21, 8.3.31, 8.2.31; php-min 8.5.6, 8.4.21, 8.3.31, 8.2.31. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami php: affected >= 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 in 8.2.31, 8.5.6, 8.4.21, 8.3.31
- Bitnami libphp: affected >= 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 in 8.2.31, 8.5.6, 8.4.21, 8.3.31
- Bitnami php-min: affected >= 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 in 8.2.31, 8.5.6, 8.4.21, 8.3.31

## Suggested inspection (read-only)
- Bitnami php: check the installed version with your package manager.
- Bitnami libphp: check the installed version with your package manager.
- Bitnami php-min: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on php, libphp, php-min.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/BIT-libphp-2026-6722 (OSV record BIT-libphp-2026-6722 lists affected ranges: Bitnami libphp >=8.2.0 =8.3.0 =8.4.0 =8.5.0 <8.5.6 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-php-2026-6722 (OSV record BIT-php-2026-6722 lists affected ranges: Bitnami php >=8.2.0 =8.3.0 =8.4.0 =8.5.0 <8.5.6 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-php-min-2026-6722 (OSV record BIT-php-min-2026-6722 lists affected ranges: Bitnami php-min >=8.2.0 =8.3.0 =8.4.0 =8.5.0 <8.5.6 (fixed))

Commands are suggestions: review each one before running it.