# OSV-2026-713: Use-of-uninitialized-value in ojph::local::tile::pull

> An attacker can cause a denial of service in the OpenJPH library by triggering a use-of-uninitialized-value error during tile processing.

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

## What is OSV-2026-713?

OSV-2026-713 is a vulnerability in openjph, published on 11 May 2026. 

### Official description

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

```
Crash type: Use-of-uninitialized-value
Crash state:
ojph::local::tile::pull
ojph::local::codestream::pull
ojph_expand_fuzz_target.cpp
```

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

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

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

## Is OSV-2026-713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: OSV-2026-713 is a vulnerability in openjph, published on 11 May 2026. 
Exploitation: There is no known exploitation of OSV-2026-713 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-713/ (Markdown: https://insights.sbomify.com/OSV-2026-713/index.md)
```

## Sources

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

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