← Back
OSV-2026-805

Vulnerability in libhevc (OSV-2026-805)

Summary

vulnerability in libhevc (OSV-2026-805). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `cdd7c565e0264d6555a2aea73a70b0a929508b2a` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **OSV-2026-805** has been found in libhevc. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade libhevc to **cdd7c565e0264d6555a2aea73a70b0a929508b2a** or later. If unsure, ask your IT team or search "libhevc OSV-2026-805" on the vendor's site.
OSV-2026-805 (libhevc) — Patched: `cdd7c565e0264d6555a2aea73a70b0a929508b2a` — 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 libhevc.
📍 Affected scope
libhevc — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **cdd7c565e0264d6555a2aea73a70b0a929508b2a**.
🛡️ 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 'libhevc' .` 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. 1
    Identify exposure identify
    grep -r 'libhevc' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `libhevc` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch
    Upgrade libhevc to cdd7c565e0264d6555a2aea73a70b0a929508b2a

    ステージング環境で cdd7c565e0264d6555a2aea73a70b0a929508b2a に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

OSS-Fuzz libhevc
[{"repo":"https:\/\/github.com\/ittiam-systems\/libhevc.git","type":"GIT","events":[{"introduced":"2f827d5db03e955540d1b59404e928bf48791d13"},{"fixed":"cdd7c565e0264d6555a2aea73a70b0a929508b2a"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →