# CVE-2026-92842: OOB read / info leak in convert.* stream filters when line-break-chars contains NUL

> An out-of-bounds read in PHP stream filters allows attackers to leak adjacent heap memory when specific line-break options are used.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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-104898, BELL-CVE-2026-92842, BIT-libphp-2026-92842, BIT-php-2026-92842, BIT-php-min-2026-92842, CLEANSTART-2026-HM12202, DEBIAN-CVE-2026-92842, ECHO-8044-4be0-76de, MINI-5q8x-xm9h-qp3f, MINI-75mw-5pwm-m436, MINI-7fgc-cwc5-2hvc, MINI-8f2p-v6wr-w3p8, MINI-9q65-rcxm-24q6, MINI-m4jj-6j9q-rfpc, MINI-mm6p-jx4p-x3r2, MINI-pg7h-2386-2825, UBUNTU-CVE-2026-92842

## What is CVE-2026-92842?

CVE-2026-92842 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 convert.base64-encode, convert.quoted-printable-encode and convert.quoted-printable-decode stream filters accept a line-break-chars option whose length is tracked separately from the string itself. The filter constructors duplicate the value with pestrdup(), which stops at the first NUL byte, while keeping the original length. When the filter later emits a line break it copies the recorded length out of the truncated allocation, reading past its end and placing adjacent heap bytes into the filter output.

Weakness: CWE-125 (Out-of-bounds Read), CWE-122 (Heap-based Buffer Overflow)

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

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-92842?

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-92842 being exploited?

There is no known exploitation of CVE-2026-92842 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-92842 and fix it if it is affected.

What it is: CVE-2026-92842 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: There is no known exploitation of CVE-2026-92842 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-92842/ (Markdown: https://insights.sbomify.com/CVE-2026-92842/index.md)
```

## Sources

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

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