# CVE-2017-9226: Memory corruption in n/a

> Heap out-of-bounds write in Oniguruma regex compilation allows attackers to execute arbitrary code or cause denial of service via malformed octal sequences.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 24 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-9226, CLSA-2025-1757666588, DEBIAN-CVE-2017-9226, GHSA-q5wh-hr49-c2mq, UBUNTU-CVE-2017-9226

## What is CVE-2017-9226?

CVE-2017-9226 is a critical memory corruption vulnerability in Php Php, published on 24 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Oniguruma 6.2.0, as used in Oniguruma-mod in Ruby through 2.4.1 and mbstring in PHP through 7.1.5. A heap out-of-bounds write or read occurs in next_state_val() during regular expression compilation. Octal numbers larger than 0xff are not handled correctly in fetch_token() and fetch_token_in_cc(). A malformed regular expression containing an octal number in the form of '\700' would produce an invalid code point value larger than 0xff in next_state_val(), resulting in an out-of-bounds write memory corruption.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2017-9226?

It affects 2 products.


Products: Oniguruma Project Oniguruma, Php Php.

## How do I fix CVE-2017-9226?

Upgrade to a fixed version.

## Is CVE-2017-9226 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2017-9224](https://insights.sbomify.com/CVE-2017-9224/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9225](https://insights.sbomify.com/CVE-2017-9225/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9227](https://insights.sbomify.com/CVE-2017-9227/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9228](https://insights.sbomify.com/CVE-2017-9228/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9229](https://insights.sbomify.com/CVE-2017-9229/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9226 and fix it if it is affected.

What it is: CVE-2017-9226 is a critical memory corruption vulnerability in Php Php, published on 24 May 2017. 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-2017-9226 in the wild and no public exploit code.

Affected product: Php Php. 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-2017-9226/ (Markdown: https://insights.sbomify.com/CVE-2017-9226/index.md)
```

## Sources

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

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