This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2026-6192 →

UBUNTU-CVE-2026-6192

Vulnerability in openjpeg (UBUNTU-CVE-2026-6192)

Summary

Vulnerability in openjpeg (UBUNTU-CVE-2026-6192). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.4.0-6ubuntu0.5 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-6192 has been found in openjpeg.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openjpeg to 2.4.0-6ubuntu0.5 or later.
If unsure, ask your IT team or search "openjpeg UBUNTU-CVE-2026-6192" on the vendor's site.

UBUNTU-CVE-2026-6192 (openjpeg)
Attack vector: local / no user interaction
Patched: 2.4.0-6ubuntu0.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in openjpeg.

📍 Affected scope

Check the vendor advisory for the affected versions of openjpeg.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.4.0-6ubuntu0.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openjpeg' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'openjpeg' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で openjpeg を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade openjpeg to 2.4.0-6ubuntu0.5
```
ステージング環境で 2.4.0-6ubuntu0.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。