# OSV-2026-710: UNKNOWN WRITE in ojph::local::precinct::parse

> A memory corruption vulnerability in the OpenJPH library allows attackers to execute arbitrary code or cause denial of service via crafted input.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026

## What is OSV-2026-710?

OSV-2026-710 is a memory corruption vulnerability in openjph, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=511393472

```
Crash type: UNKNOWN WRITE
Crash state:
ojph::local::precinct::parse
ojph::local::resolution::parse_one_precinct
ojph::local::tile::parse_tile_header
```

## Which versions are affected by OSV-2026-710?

1 open source package ship an affected version, including openjph.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openjph` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2026-710?

No fix has been published for OSV-2026-710 yet. Limit exposure of the affected software until one is available.

## Is OSV-2026-710 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2026-710 and fix it if it is affected.

What it is: OSV-2026-710 is a memory corruption vulnerability in openjph, published on 11 May 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 OSV-2026-710 in the wild and no public exploit code.

Affected packages and fixed versions:
- openjph (OSS-Fuzz): affected all versions; no fix listed

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

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2026-710

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