Vulnerability in libde265 (UBUNTU-CVE-2026-49337)

Summary

Vulnerability in libde265 (UBUNTU-CVE-2026-49337). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.0.2-2ubuntu0.16.04.1~esm6 or later.

Original description

The description as published by the source.

libde265 is an open source implementation of the h.265 video codec. Prior to version 1.0.20, a crafted sequence of H.265 NAL units causes decoder_context::read_slice_NAL() (libde265/decctx.cc:481) to attach slice headers to a finished picture object that has no active image unit, resulting in attacker-controlled unbounded heap growth. The retained headers are never freed until the picture is released, which may not happen during continuous streaming. Version 1.0.20 patches the 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-49337 has been found in libde265.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libde265 to 1.0.2-2ubuntu0.16.04.1~esm6 or later.
If unsure, ask your IT team or search "libde265 UBUNTU-CVE-2026-49337" on the vendor's site.

UBUNTU-CVE-2026-49337 (libde265)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.0.2-2ubuntu0.16.04.1~esm6 — 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 libde265.

📍 Affected scope

Check the vendor advisory for the affected versions of libde265.

🔥 Severity

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

🔧 How to fix

Update to 1.0.2-2ubuntu0.16.04.1~esm6.

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

Affected packages

Ubuntu:Pro:16.04:LTS libde265

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.2-2ubuntu0.16.04.1~esm6"}]}]

Ubuntu:Pro:18.04:LTS libde265

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.2-2ubuntu0.18.04.1~esm6"}]}]

Ubuntu:Pro:20.04:LTS libde265

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.4-1ubuntu0.4+esm2"}]}]

Ubuntu:Pro:22.04:LTS libde265

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.8-1ubuntu0.3+esm2"}]}]

Ubuntu:24.04:LTS libde265

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.15-1ubuntu0.1"}]}]

Ubuntu:25.10 libde265

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:26.04:LTS libde265

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.16-1ubuntu0.1~esm1"}]}]

References

advisory ubuntu.com
report ubuntu.com
report cve.org
report github.com