# CVE-2026-6192: uclouvain openjpeg pi.c opj_pi_initialise_encode integer overflow

> A local attacker can trigger an integer overflow in OpenJPEG's encoding initialization, potentially causing a denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2026
- **Updated:** 21 May 2026
- **Also known as:** ALPINE-CVE-2026-6192, AZL-83042, BELL-CVE-2026-6192, DEBIAN-CVE-2026-6192, ECHO-a92e-9791-007a, GHSA-6jfp-5ggc-pgmx, JLSEC-2026-1267, OESA-2026-1959, OESA-2026-2022, OESA-2026-2023, OESA-2026-2024, OESA-2026-2025, UBUNTU-CVE-2026-6192, USN-8252-1

## What is CVE-2026-6192?

CVE-2026-6192 is a medium-severity vulnerability in uclouvain openjpeg, published on 13 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was identified in uclouvain openjpeg up to 2.5.4. This impacts the function opj_pi_initialise_encode in the library src/lib/openjp2/pi.c. The manipulation leads to integer overflow. The attack must be carried out locally. The exploit is publicly available and might be used. The identifier of the patch is 839936aa33eb8899bbbd80fda02796bb65068951. It is suggested to install a patch to address this issue.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-189

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


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

Apply the vendor's patch.

## Is CVE-2026-6192 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6192 is a medium-severity vulnerability in uclouvain openjpeg, published on 13 Apr 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-6192 exists.

Affected product: uclouvain openjpeg. 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-6192/ (Markdown: https://insights.sbomify.com/CVE-2026-6192/index.md)
```

## Sources

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

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