# CVE-2026-89157: Memory corruption in PCRE2

> An out-of-bounds write in PCRE2 on 32-bit platforms allows attackers to cause memory corruption via large patterns, potentially leading to code execution or crashes.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** ALPINE-CVE-2026-89157, AZL-100059, AZL-101114, AZL-101748, AZL-101760, AZL-101811, AZL-101826, BELL-CVE-2026-89157, DEBIAN-CVE-2026-89157, ECHO-6a6d-27a2-7d3c, GHSA-797w-fgfq-r75v, GHSA-q8g2-wprr-34m9, MINI-4j38-wp2f-p6jv, ROOT-OS-ALPINE-315-CVE-2026-89157, UBUNTU-CVE-2026-89157

## What is CVE-2026-89157?

CVE-2026-89157 is a medium-severity memory corruption vulnerability in PCRE2, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PCRE2 before 10.48, on 32-bit platforms, has a pcre2_pattern_convert out-of-bounds write when an attacker can provide a large pattern.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Pcre Pcre2.

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

Upgrade to a fixed version.

## Is CVE-2026-89157 being exploited?

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

## Other vulnerabilities in PCRE2

- [CVE-2017-8786](https://insights.sbomify.com/CVE-2017-8786/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-8399](https://insights.sbomify.com/CVE-2017-8399/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-41409](https://insights.sbomify.com/CVE-2022-41409/): Integer overflow in n/a (high 7.5)
- [CVE-2026-89161](https://insights.sbomify.com/CVE-2026-89161/): Use after free in PCRE2 (high 7.4)
- [CVE-2025-58050](https://insights.sbomify.com/CVE-2025-58050/): PCRE2: heap-buffer-overflow read in match_ref due to missing boundary restoration in SCS (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89157 is a medium-severity memory corruption vulnerability in PCRE2, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-89157 exists.

Affected product: PCRE2. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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