# CVE-2025-14181: Integer overflow to buffer overflow in soap HTTP parsing

> A malicious SOAP server can trigger a heap buffer overflow in the PHP SOAP client via integer overflow, potentially allowing remote code execution.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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:** 25 Sep 2026
- **Also known as:** AZL-104910, BELL-CVE-2025-14181, BIT-libphp-2025-14181, BIT-php-2025-14181, BIT-php-min-2025-14181, CLEANSTART-2026-WW44198, DEBIAN-CVE-2025-14181, ECHO-cd7b-3399-46aa, MINI-224x-j9r2-xw49, MINI-23c2-7pgq-r3f8, MINI-2649-574r-4jc7, MINI-67r8-h55p-qcm7, MINI-p66g-756m-jhjp, MINI-v8pw-c2hm-82mp, MINI-wc74-x997-f5rc, MINI-x6w5-jw6j-334c, UBUNTU-CVE-2025-14181

## What is CVE-2025-14181?

CVE-2025-14181 is a medium-severity 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

The SOAP HTTP client guards its response buffer growth with a check that relies on signed integer overflow, which is undefined behaviour and is not guaranteed to trigger. When the check is optimised away, a malicious SOAP server can make the client allocate a buffer far smaller than the data it then writes into it, producing a heap buffer overflow.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-14181?

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-2025-14181?

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-2025-14181 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14181 exists.

## 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-2025-14181 and fix it if it is affected.

What it is: CVE-2025-14181 is a medium-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14181 exists.

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-2025-14181/ (Markdown: https://insights.sbomify.com/CVE-2025-14181/index.md)
```

## Sources

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

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