# CVE-2026-91765: SOAP: Unbounded Recursion in Server-Side cleanup_xml_node

> An unauthenticated attacker can crash the PHP SOAP server by sending deeply nested XML elements, causing stack exhaustion via unbounded recursion.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** AZL-104919, BELL-CVE-2026-91765, BIT-libphp-2026-91765, BIT-php-2026-91765, BIT-php-min-2026-91765, CLEANSTART-2026-PP41218, DEBIAN-CVE-2026-91765, ECHO-2fbd-f0a2-587a, MINI-23mx-2hfq-x5fv, MINI-39hw-3m4c-m8vh, MINI-7cw9-pcqg-22m3, MINI-7hhx-6q54-v4f2, MINI-85rf-6w64-mhxv, MINI-chr7-245m-rmp2, MINI-qf87-549p-hrfr, MINI-qrjp-w92g-6h76, UBUNTU-CVE-2026-91765

## What is CVE-2026-91765?

CVE-2026-91765 is a high-severity denial of service vulnerability in Php Php, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

cleanup_xml_node() in the SOAP XML parser recurses once per XML nesting level with no depth limit. An unauthenticated attacker can post a SOAP request containing tens of thousands of nested elements to any SoapServer endpoint, exhaust the stack and crash the process. The same unbounded recursion exists in the SOAP value decoder and in the WSDL node search helper.

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2026-91765?

3 open source packages ship an affected version, including libphp, php and php-min. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libphp` | Bitnami | From 8.2.0 | 8.2.34, 8.3.35, 8.4.26, 8.5.11 |
| `php` | Bitnami | From 8.2.0 | 8.2.34, 8.3.35, 8.4.26, 8.5.11 |
| `php-min` | Bitnami | From 8.2.0 | 8.2.34, 8.3.35, 8.4.26, 8.5.11 |

Products: Php Php.

## How do I fix CVE-2026-91765?

Upgrade libphp to a fixed version for your release line: 8.2.34, 8.3.35, 8.4.26 or 8.5.11.

## Is CVE-2026-91765 being exploited?

There is no known exploitation of CVE-2026-91765 in the wild and no public exploit code.

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-91765 and fix it if it is affected.

What it is: CVE-2026-91765 is a high-severity denial of service vulnerability in Php Php, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-91765 in the wild and no public exploit code.

Affected packages and fixed versions:
- libphp (Bitnami): affected from 8.2.0; fixed in 8.2.34, 8.3.35, 8.4.26, 8.5.11
- php (Bitnami): affected from 8.2.0; fixed in 8.2.34, 8.3.35, 8.4.26, 8.5.11
- php-min (Bitnami): affected from 8.2.0; fixed in 8.2.34, 8.3.35, 8.4.26, 8.5.11

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-91765/ (Markdown: https://insights.sbomify.com/CVE-2026-91765/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-91765
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-91765
- OSV: https://osv.dev/vulnerability/CVE-2026-91765

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-91765/
Summaries are generated and may contain mistakes; the official description above is the record.