Vulnerability DatabaseCVE-2026-129506

CVE-2026-129506: 
PHP vulnerability analysis and mitigation

Overview

CVE-2026-129506 is a use-after-free (UAF) vulnerability in PHP's SOAP extension triggered when processing XML documents containing a Document Type Definition (DTD) with entity references in attribute values. The SOAP extension prematurely frees the DTD during XML document cleanup while attribute values may still reference entities owned by it, enabling reads of freed memory. Affected versions span PHP 8.2.0–8.2.35, 8.3.0–8.3.36, 8.4.0–8.4.27, and 8.5.0–8.5.12; fixed versions are 8.2.36, 8.3.37, 8.4.28, and 8.5.13. It carries a CVSS v4.0 base score of 6.3 (Medium) (GitHub Advisory, Feedly). The vulnerability was published on November 19, 2026.

Technical details

The root cause is CWE-416 (Use After Free): PHP's XML cleanup routine frees the DTD object while attribute values parsed from the document can still hold references to entities owned by that DTD. When those attributes are subsequently processed, the SOAP extension reads already-freed memory. A secondary consequence is that freeing the DTD removes it from the parsed document structure, bypassing the SOAP server's built-in check that rejects documents containing a DTD — allowing DTD-bearing documents to pass through undetected. The issue predates and is distinct from CVE-2026-91765, affecting all supported PHP 8.x branches. Exploitation requires the SOAP extension to be enabled and the application to process attacker-controlled SOAP XML, WSDL, or imported schema content; notably, authentication does not protect an endpoint if the application parses the SOAP request before authenticating (GitHub Advisory).

Impact

The confirmed impact is denial of service: a crafted SOAP request can crash the PHP worker process, and repeated requests can sustain service disruption. The DTD bypass also means that applications relying on the SOAP server's built-in DTD rejection as a security control are silently exposed. Memory disclosure and arbitrary code execution have not been confirmed, though the original report noted corrupted type information after freed memory was reused, leaving open the theoretical possibility of more severe outcomes (GitHub Advisory, Feedly).

Exploitability

No public proof-of-concept exploit code or in-the-wild exploitation has been reported as of the disclosure date. The EPSS score is 0.0, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The NVD SSVC assessment classifies exploitation as "none" and the attack as non-automatable, reflecting the requirement for specific deployment conditions (SOAP extension enabled, attacker-reachable endpoint or attacker-controlled WSDL/schema) (GitHub Advisory, Feedly).

Exploitation steps

  1. Reconnaissance: Identify internet-facing PHP applications exposing SOAP endpoints (e.g., via ?wsdl query strings, service discovery, or Shodan/Censys searches for SOAP-related HTTP responses) running PHP 8.2.x < 8.2.36, 8.3.x < 8.3.37, 8.4.x < 8.4.28, or 8.5.x < 8.5.13.
  2. Craft malicious XML payload: Construct a SOAP XML request body that includes a DTD declaration with an entity definition, and references that entity within an attribute value — for example:
<?xml version="1.0"?>
<!DOCTYPE foo [
  <!ENTITY xxe "malicious">
]>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Body attr="&xxe;">
    ...
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
  1. Send crafted request: Submit the malicious SOAP request via HTTP POST to the target endpoint. Because the DTD is freed before attribute processing completes, the PHP process reads freed memory, triggering a crash.
  2. Repeat for DoS: Send repeated crafted requests to sustain denial of service against the PHP worker pool.
  3. Alternative vector: If the application loads attacker-controlled WSDL or imported schema documents, supply a malicious WSDL containing a DTD with entity references to trigger the same condition without direct SOAP endpoint access (GitHub Advisory).

Indicators of compromise

  • Network: Unusual HTTP POST requests to SOAP endpoints containing <!DOCTYPE or <!ENTITY strings in the request body; repeated SOAP requests from a single source IP causing process restarts.
  • Logs: PHP error logs (php_error.log, php-fpm.log) showing segmentation faults or "use after free" errors originating from the SOAP extension; web server access logs with repeated 500 or 502 responses to SOAP endpoint URLs.
  • Process: Unexpected termination or restart of PHP-FPM worker processes; core dump files generated in the PHP working directory following SOAP request processing.
  • Application: SOAP endpoints returning unexpected errors or becoming intermittently unavailable; application logs showing XML parsing failures related to DTD processing (GitHub Advisory).

Mitigation and workarounds

Upgrade to the patched PHP releases: 8.2.36, 8.3.37, 8.4.28, or 8.5.13, which keep the DTD alive for the full lifetime of the XML document and restore the SOAP DTD rejection check. As interim mitigations: restrict or disable access to SOAP endpoints where not required; load WSDL and imported schemas only from trusted, controlled sources; and implement a pre-parse filter to reject SOAP request bodies containing a DTD before they reach the SOAP extension (note that a simple text search is insufficient — the filter must handle all XML encodings and request-body transformations accepted by the application) (GitHub Advisory).

Community reactions

The vulnerability received coverage from multiple security-focused outlets shortly after its November 19, 2026 disclosure, including Infosecurity Magazine, CyberSecurityNews, Patchstack (with WordPress-specific guidance), and Meterpreter.org. AlmaLinux published a blog post addressing the PHP security release for their platform. Community discussion on dev.to and dev-talk.com highlighted the November 2026 PHP security release broadly. No notable individual researcher commentary or significant social media controversy has been identified beyond standard patch-release coverage (Patchstack, Infosecurity Magazine).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

php8.2: 8.2.36-1~deb12u1

Fixed

sid

php8.4: 8.4.28-2

Fixed

trixie

php8.4: 8.4.28-1~deb13u1

Fixed

Ubuntu

Fixed

bionic (esm-infra)

php7.2: 7.2.24-0ubuntu0.18.04.17+esm15

Fixed

devel

php8.5

Affected

focal (esm-infra)

php7.4: 7.4.3-4ubuntu2.29+esm6

Fixed

jammy

php8.1: 8.1.2-1ubuntu2.29

Fixed

noble

php8.3: 8.3.6-0ubuntu0.24.04.14

Fixed

resolute

php8.5: 8.5.4-0ubuntu1.6

Fixed

trusty (esm-infra-legacy)

php5: 5.5.9+dfsg-1ubuntu4.29+esm19

Fixed

xenial (esm-infra-legacy)

php7.0: 7.0.33-0ubuntu0.16.04.16+esm23

Fixed

RHEL / CentOS

Fixed

RHEL 8

php:7.4/php.src

Affected

RHEL 9

:appstream:php-0:8.2-9080020261120141350.9.src

Fixed

RHEL 10

php8.4-0:8.4.28-1.el10_2.src

Fixed

Alpine

Fixed

edge

php83: 8.3.37-r0, 8.5.13-r0

Fixed

Source: This report was generated using AI

Related PHP vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-104883HIGH7.2
  • PHP logoPHP
  • contao/core-bundle
NoYesNov 20, 2026
GHSA-vw9g-2c4c-g767MEDIUM6.8
  • PHP logoPHP
  • livewire/livewire
NoYesNov 21, 2026
CVE-2026-104882MEDIUM6.5
  • PHP logoPHP
  • cpe:2.3:a:contao:contao
NoYesNov 20, 2026
GHSA-2g6w-c7gx-fxj8MEDIUM5.4
  • PHP logoPHP
  • guzzlehttp/guzzle
NoYesNov 21, 2026
CVE-2026-104884MEDIUM5.4
  • PHP logoPHP
  • composer://contao/contao
NoYesNov 20, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management