Vulnerability in libheif (USN-8454-1)

Summary

vulnerability in libheif (USN-8454-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1.1.0-2ubuntu0.1~esm3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **USN-8454-1** has been found in libheif. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade libheif to **1.1.0-2ubuntu0.1~esm3** or later. If unsure, ask your IT team or search "libheif USN-8454-1" on the vendor's site.

USN-8454-1 (libheif) — Patched: `1.1.0-2ubuntu0.1~esm3` — 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.

📍 Affected scope

libheif — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **1.1.0-2ubuntu0.1~esm3**.

🛡️ 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 (7 steps)

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 し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade libheif to 1.1.0-2ubuntu0.1~esm3
```
ステージング環境で 1.1.0-2ubuntu0.1~esm3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:18.04:LTS libheif

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.0-2ubuntu0.1~esm3"}]}]

Ubuntu:Pro:20.04:LTS libheif

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

Ubuntu:Pro:22.04:LTS libheif

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.12.0-2ubuntu0.1~esm3"}]}]

Ubuntu:24.04:LTS libheif

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

Ubuntu:25.10 libheif

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

Ubuntu:26.04:LTS libheif

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

References

advisory https://ubuntu.com/security/notices/USN-8454-1
report https://ubuntu.com/security/CVE-2026-3950
report https://ubuntu.com/security/CVE-2026-32738
report https://ubuntu.com/security/CVE-2026-32739
report https://ubuntu.com/security/CVE-2026-32740
report https://ubuntu.com/security/CVE-2026-32741
report https://ubuntu.com/security/CVE-2026-32814
report https://ubuntu.com/security/CVE-2026-32882
report https://ubuntu.com/security/CVE-2026-41069
report https://ubuntu.com/security/CVE-2026-41071