Vulnerability in libheif (UBUNTU-CVE-2026-47709)

Summary

Vulnerability in libheif (UBUNTU-CVE-2026-47709). Risk of unauthorized operations or information disclosure. Exploitable via uncC. Mitigation: upgrade to 1.17.6-1ubuntu4.6 or later.

Original description

The description as published by the source.

libheif is a HEIF and AVIF file format decoder and encoder. Versions prior to 1.22.0 crashes in the public C API heif_image_handle_get_image_tiling() when a malformed uncompressed HEIF image item has an associated uncC property but no associated ispe property. In debug builds this trips the ispe && uncC assertion in ImageItem_uncompressed::get_heif_image_tiling(). In a release/NDEBUG ASan build, the same file causes a null pointer read at address 0xa8. Version 1.22.0 fixes 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-47709 has been found in libheif.
Attackers can target a specific entry point like uncC over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libheif to 1.17.6-1ubuntu4.6 or later.
If unsure, ask your IT team or search "libheif UBUNTU-CVE-2026-47709" on the vendor's site.

UBUNTU-CVE-2026-47709 (libheif)
Attack vector: local / unauthenticated
Attack surface: uncC / ispe
Patched: 1.17.6-1ubuntu4.6 — 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 libheif. Attackers reach the vulnerable code path via uncC without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of libheif. Attack surface: uncC / ispe.

🔥 Severity

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

🔧 How to fix

Update to 1.17.6-1ubuntu4.6.

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

Affected packages

Ubuntu:24.04:LTS libheif

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.17.6-1ubuntu4.6"}]}]

Ubuntu:25.10 libheif

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

Ubuntu:26.04:LTS libheif

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

References

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